Re: dpage/pgadmin4 container failed in rancher/kubernetes , but worksdirectly from dockerd - Mailing list pgadmin-support

From Dave Page
Subject Re: dpage/pgadmin4 container failed in rancher/kubernetes , but worksdirectly from dockerd
Date
Msg-id CA+OCxoy577y9o34GW5ggP5xX=PSoHJSfCEfi8SyH05F1dHi6Eg@mail.gmail.com
Whole thread Raw
In response to dpage/pgadmin4 container failed in rancher/kubernetes , but worksdirectly from dockerd  (Dmitry Zhirkov <dmitry.zhirkov@gmail.com>)
List pgadmin-support
Hi

On Fri, Jul 12, 2019 at 2:11 PM Dmitry Zhirkov <dmitry.zhirkov@gmail.com> wrote:

Traceback (most recent call last):
  File "run_pgadmin.py", line 4, in <module>
    from pgAdmin4 import app
  File "/pgadmin4/pgAdmin4.py", line 131, in <module>
    server_port = int(port)
ValueError: invalid literal for int() with base 10: 'tcp://10.43.151.247:80'

That would suggest that PGADMIN_PORT is set in the environment to 'tcp://10.43.151.247:80'. If you set that environment variable (and in a containerised environment, I cannot think of a compelling reason to do so - you should use PGADMIN_LISTEN_PORT), it must be set to a valid port number only.

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

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

pgadmin-support by date:

Previous
From: Dmitry Zhirkov
Date:
Subject: dpage/pgadmin4 container failed in rancher/kubernetes , but worksdirectly from dockerd
Next
From: Dave Page
Date:
Subject: Re: dpage/pgadmin4 container failed in rancher/kubernetes , but worksdirectly from dockerd