docker beyond wiki fails here

[CaptainBlood]

Docker noob here.

Wiki achieved fine.

But trying pgadmin4 official docker image fails.

IIRC app should be accessible through http://localhost:80

Code: Select all

EDIT: sysctl net.ipv4.ip_forward=1

is here too.

Connection is rejected.

telnet detects something is there.

No idea how to investigate...

Any simpler docker image I could use to test my docker install?

Thks 4 ur attention, interest & support.

[pingtoo]

Beside unreachable, is there any other error?

Does the container actually running?

The simple one could be

Code: Select all

docker run -it busybox

You don't need to manually change forwarding, docker will do that for you.

[CaptainBlood]

Container is gone after ~ 2 mn.

Short duration may indicate init issue?

Thks 4 ur attention,interest & support.

[CaptainBlood]

Code: Select all

docker run -it busybox

runs fine too, like with the wiki test.

Thks 4 ur attention, interest & support.

[pingtoo]

Container is gone after ~ 2 mn.

Short duration may indicate init issue?

Thks 4 ur attention,interest & support.

If you start your container without the '-rm' option then, there should be some log for the container. can you try

Code: Select all

docker logs <container name>

to see if anything were register?

[CaptainBlood]

Code: Select all

>>> Emerging (1 of 1) app-containers/docker-24.0.5-r1::gentoo
 * docker-24.0.5.tar.gz BLAKE2B SHA512 size ;-) ...                      [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.9.2-gentoo-docker
 * Checking for suitable kernel configuration options ...
 *   CONFIG_LEGACY_VSYSCALL_NONE enabled: 		Containers with <=glibc-2.13 will not work
 *   CONFIG_CGROUP_HUGETLB:	 is not set when it should be.           [ !! ]
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.

CGROUP_HUGETLB can't be activated here. Wiki says optional.

Maybe I should try default kernel .config?

Thks 4 ur attention, interest & support.

[CaptainBlood]

Code: Select all

docker logs 6d31a3a915ea3fa75ece45ed393dc73c44267fdf3f9820cb75ae02041dcd37ff
NOTE: Configuring authentication for SERVER mode.

pgAdmin 4 - Application Initialisation
======================================

postfix/postlog: starting the Postfix mail system
[2024-05-26 17:11:55 +0000] [1] [INFO] Starting gunicorn 20.1.0
[2024-05-26 17:11:55 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:11:56 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:11:57 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:11:58 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:11:59 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:12:00 +0000] [1] [ERROR] Can't connect to ('::', 80)

Thks 4 ur attention, interest & support.

[pingtoo]

Code: Select all

docker logs 6d31a3a915ea3fa75ece45ed393dc73c44267fdf3f9820cb75ae02041dcd37ff
NOTE: Configuring authentication for SERVER mode.

pgAdmin 4 - Application Initialisation
======================================

postfix/postlog: starting the Postfix mail system
[2024-05-26 17:11:55 +0000] [1] [INFO] Starting gunicorn 20.1.0
[2024-05-26 17:11:55 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:11:56 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:11:57 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:11:58 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:11:59 +0000] [1] [ERROR] Retrying in 1 second.
[2024-05-26 17:12:00 +0000] [1] [ERROR] Can't connect to ('::', 80)

Thks 4 ur attention, interest & support.

trying pgadmin4 official docker image

, which image? A image exist on docker hub does not make if official, anybody can publish images into docker hub.

Can you share the command used for start this container? or if you want you can remove this container, but start a new container. but share the command use to start new container.

It is unlikely your kernel need to changes in order to run docker, however I don't know if there something required for run pgadmin4. have you find anything defined by pgadmin4 developler?

[CaptainBlood]

Code: Select all

 docker run -p 80:80     -e 'PGADMIN_DEFAULT_EMAIL=user@domain.com'     -e 'PGADMIN_DEFAULT_PASSWORD=SuperSecret'     -d dpage/pgadmin4

Thks 4 ur attention, interest & support.

[CaptainBlood]

Code: Select all

 docker run   -e 'PGADMIN_DEFAULT_EMAIL=user@domain.com'     -e 'PGADMIN_DEFAULT_PASSWORD=SuperSecret'     -d dpage/pgadmin4

without any port fails the same.

Thks 4 ur attention, interest & support.

[CaptainBlood]

Code: Select all

eixi app-containers/docker
[I] app-containers/docker
     Available versions:  24.0.5-r1^sti ~24.0.6^sti ~24.0.7-r1^sti ~25.0.1^sti ~25.0.4^sti ~26.1.0-r1^sti {apparmor btrfs +container-init device-mapper overlay seccomp selinux systemd}
     Installed versions:  24.0.5-r1^sti(19:59:09 26/05/2024)(container-init -apparmor -btrfs -device-mapper -overlay -seccomp -selinux -systemd)

Stable here.

Thks 4 ur attention, interest & support.

[CaptainBlood]

[quote="CaptainBlood"]

Code: Select all

[2024-05-26 17:12:00 +0000] [1] [ERROR] Can't connect to ('::', 80)

/quote]

:: ... Could that be IP6 thingie?

net-vpn/riseup-vpn has the same issue, failed to work if not IP4+IP6.

Thks 4 ur attention, interest & support.

[pingtoo]

Code: Select all

 docker run   -e 'PGADMIN_DEFAULT_EMAIL=user@domain.com'     -e 'PGADMIN_DEFAULT_PASSWORD=SuperSecret'     -d dpage/pgadmin4

without any port fails the same.

Thks 4 ur attention, interest & support.

I think your current situation is not Gentoo/Docker issue, it is container configuration issue.

So depend on what you like to do, Do you like to resolve the issue for not able start pgadmin4? or you prefer to learn more about docker debugging strategy?

For quick start pgadmin4, I suggest you change the binding to only IPv4, I have seem some docker images have application limit so bind to IPv6 will cause problem, so you can try

Code: Select all

docker run -p 0.0.0.0:80:80 -e PGADMIN_DISABLE_POSTFIX=1 -e ...

This will disable the postfix start in the entrypoint.sh and will let the script continue to start gunicorn for web service. If that does not work try

Code: Select all

docker run -p 0.0.0.0:80:80 -e PGADMIN_DISABLE_POSTFIX=1 --sysctl net.ipv6.conf.all.disable_ipv6=1 -e...

This is to ensure the container instance not using IPv6 stack.

If you wish to know more about docker debugging, we can try to start the container with shell (i.e. will not run the entrypoint.sh) In this way we can examine the container environment and execute step by step follow the entrypoint.sh to understand where exactly the cause.

Code: Select all

docker run -it --entrypoint /bin/sh -e...

[pingtoo]

There apparently have another container environment variable "PGADMIN_LISTEN_ADDRESS=", so please also try to add it in to command line for example

Code: Select all

docker run -p 0.0.0.0:80:80 -e PGADMIN_DISABLE_POSTFIX=1 -e PGADMIN_LISTEN_ADDRESS=0.0.0.0 -e ...

[CaptainBlood]

That's what so nice on Gentoo forums...
Unexpected and interesting ideas and proposals. +1

AFA quick start is concerned, IP4+IP6 made it run.

AFA pgadmin4 Desktop is concerned, I never found out how to (e)build version since v7.
Arch & Debian have binpkg though.

Thks 4 ur attention, interest & support.

[pingtoo]

AFA quick start is concerned, IP4+IP6 made it run.

Mean you made changes to system (or kernel) to enable/disable IPv6?

[CaptainBlood]

Kernel level.

Had a minimal kernel for riseup-vpn which requires IP4+6.
Still have to retrieve and remove riseup-vpn only kernel options.

Docker is pgadmin4 Server, not Desktop.

Thks 4 ur attention, interest & support.

[pingtoo]

Kernel level.

Had a minimal kernel for riseup-vpn which requires IP4+6.
Still have to retrieve and remove riseup-vpn only kernel options.

Docker is pgadmin4 Server, not Desktop.

Thks 4 ur attention, interest & support.

Thanks for the information. Hope your docker journey smooth and prosper