Re: Docker image not running on IPv6-disabled systems

From: Diego Augusto Molina <diegoaugustomolina(at)gmail(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: Docker image not running on IPv6-disabled systems
Date: 2019-01-29 05:41:34
Message-ID: CAGOxLdGq8v9LkxmJ=eY6agTU7gTaMVLcBnJqYBTOYSjLbWbUrw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hi, Dave

On 1/22/19, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hi
>
> On Wed, Jan 16, 2019 at 12:41 PM Diego Augusto Molina
> <diegoaugustomolina(at)gmail(dot)com> wrote:
>>
>> Here's the patch, sorry for the bad manners.
>
> That effectively reverts the fix committed to resolve this doesn't it?
> https://redmine.postgresql.org/issues/3392

Yeah, it really does.

>
> Maybe the way to go is to expose the bind address (or some options to
> control it) in variables that can be set at launch time, leaving the
> default as-is.
>
> Thoughts?

Sounds like the way to go. There goes the new humble patch for the
"/entrypoint.sh", which runs just fine. The new environment variable
is named PGADMIN_LISTEN_ADDRESS and defaults to "[::]". Tested with
the following Dockerfile:

$Dockerfile$
FROM dpage/pgadmin4:latest

RUN sed -i 's/\[::\]/${PGADMIN_BIND_ADDRESS:-[::]}/' /entrypoint.sh

# This is just candy but could be added for ease of use in debugging:
SHELL ["/bin/sh"]

$Dockerfile$

Thanks a lot!

>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Attachment Content-Type Size
entrypoint.sh.patch text/x-patch 948 bytes

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Arni Kromić 2019-01-29 09:54:32 Some pgAdmin 4 (4.1) bugs
Previous Message Khushboo Vashi 2019-01-29 03:57:07 Re: Progress window not closing