Re: pgadmin, docker and ipv6 - Mailing list pgadmin-hackers

From Dave Page
Subject Re: pgadmin, docker and ipv6
Date
Msg-id CA+OCxoyG_HZYYV8WfWshNBy4tjj25mOA8peUJVFh48nP-aEPww@mail.gmail.com
Whole thread Raw
In response to Re: pgadmin, docker and ipv6  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
Thanks!

On Wed, May 30, 2018 at 5:53 PM, Александр Шишенко <alex@shishenko.com> wrote:
 
31.05.2018, 00:47, "Dave Page" <dpage@pgadmin.org>:
Hi
 
On Sun, May 27, 2018 at 7:13 AM, Александр Шишенко <alex@shishenko.com> wrote:
Hello,
 
I was running my pgadmin4 v2 on my ipv6-only subnet using docker image. After the update, I noticed, that you have changed your webserver from Apache to gunicorn, and it is configured to listen only on ipv4 network (0.0.0.0), so it is unreachable from my network without using docker-proxy (and I can't use that on my configuration).
 
Please, consider switching to dual-stack networking in your configuration. It is just as simple as changing '--bind 0.0.0.0:${PGADMIN_LISTEN_PORT:-443}' to '--bind [::]:${PGADMIN_LISTEN_PORT:-443}' in your pkg/docker/entrypoint.sh.
-- 
 
 
Can you log this on the tracker please? https://redmine.postgresql.org/projects/pgadmin4/issues/new
 
Thanks!
 
 
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
 
 
-- 



--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: pgadmin, docker and ipv6
Next
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Ensure backup/restore/maintenance work via SSHtunnel