Re: pgadmin, docker and ipv6
От | Dave Page |
---|---|
Тема | Re: pgadmin, docker and ipv6 |
Дата | |
Msg-id | CA+OCxoyG_HZYYV8WfWshNBy4tjj25mOA8peUJVFh48nP-aEPww@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgadmin, docker and ipv6 (Dave Page <dpage@pgadmin.org>) |
Список | pgadmin-hackers |
Thanks!
On Wed, May 30, 2018 at 5:53 PM, Александр Шишенко <alex@shishenko.com> wrote:
Sure, here is the ticket: https://redmine.postgresql.org/issues/3392 31.05.2018, 00:47, "Dave Page" <dpage@pgadmin.org>:HiOn 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:-44 3}' 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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgadmin-hackers по дате отправления: