| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | dmitry(dot)zhirkov(at)gmail(dot)com |
| Cc: | "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: dpage/pgadmin4 container failed in rancher/kubernetes , but works directly from dockerd |
| Date: | 2019-07-12 13:21:22 |
| Message-ID: | CA+OCxoy577y9o34GW5ggP5xX=PSoHJSfCEfi8SyH05F1dHi6Eg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Hi
On Fri, Jul 12, 2019 at 2:11 PM Dmitry Zhirkov <dmitry(dot)zhirkov(at)gmail(dot)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 <http://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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2019-07-17 08:06:46 | Re: dpage/pgadmin4 container failed in rancher/kubernetes , but works directly from dockerd |
| Previous Message | Dmitry Zhirkov | 2019-07-12 13:10:45 | dpage/pgadmin4 container failed in rancher/kubernetes , but works directly from dockerd |