Container UP but not listening

[c3h5o9n]

Hello,

npm container is up but does not listen on tcp ports 80, 81, 443. These ports are not used on the docker host (the container would not go up). Using debian 12, docker-compose version 1.29.2

Here is compose file:

version: '3.8'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt`

Here are docker logs:

❯ Configuring npm user ...
❯ Configuring npm group ...
❯ Checking paths ...
❯ Setting ownership ...

Here is what shows netstat in the container:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.11:38683        0.0.0.0:*               LISTEN      -
udp        0      0 127.0.0.11:43637        0.0.0.0:*                           -
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node   PID/Program name     Path
unix  3      [ ]         STREAM     CONNECTED     11985518 59/s6-sudoc
unix  2      [ ACC ]     STREAM     LISTENING     11985509 38/s6-ipcserverd     s
unix  3      [ ]         STREAM     CONNECTED     11986497 60/s6-sudod          s

Here is what shows ps in the container:

USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           1  0.0  0.0    208    64 ?        Ss   08:20   0:00 /package/admin/s6/command/s6-svscan -d4 -- /run/service
root          14  0.0  0.0   2388  1608 ?        Ss   08:21   0:00 /bin/sh -e /run/s6/basedir/scripts/rc.init top
root          15  0.0  0.0    212    64 ?        S    08:21   0:00 s6-supervise s6-linux-init-shutdownd
root          17  0.0  0.0    200     4 ?        Ss   08:21   0:00 /package/admin/s6-linux-init/command/s6-linux-init-shutdownd -c /run/s6/basedir -g 3000 -C -B
root          26  0.0  0.0    212    64 ?        S    08:21   0:00 s6-supervise frontend
root          27  0.0  0.0    212    68 ?        S    08:21   0:00 s6-supervise s6rc-oneshot-runner
root          28  0.0  0.0    212    68 ?        S    08:21   0:00 s6-supervise nginx
root          29  0.0  0.0    212    68 ?        S    08:21   0:00 s6-supervise backend
root          30  0.0  0.0    212    64 ?        S    08:21   0:00 s6-supervise s6rc-fdholder
root          34  0.0  0.0    216    68 ?        S    08:21   0:00 s6-rc -v1 -u -t 0 -- change top
root          38  0.0  0.0    188     4 ?        Ss   08:21   0:00 /package/admin/s6/command/s6-ipcserverd -1 -- /package/admin/s6/command/s6-ipcserver-access -v0 -E -l0 -i data/rules -- /package/admin/s6/command/s6-sudod -t 30000 -- /package/admin/s6-rc/command/s6-rc-
root          59  0.0  0.0    196    48 ?        S    08:21   0:00 /package/admin/s6-2.11.3.2/command/s6-sudoc -e -t 30000 -T 0 -- up 5
root          60  0.0  0.0    208    60 ?        S    08:21   0:00 /package/admin/s6/command/s6-sudod -t 30000 -- /package/admin/s6-rc/command/s6-rc-oneshot-run -l ../.. --
root          61  0.0  0.0   3736  2916 ?        S    08:21   0:00 bash /etc/s6-overlay/s6-rc.d/prepare/00-all.sh
root         110  0.0  0.0   2412  1592 ?        D    08:22   0:01 chown -R 0:0 /opt/certbot
root         111  0.0  0.0   4000  3212 pts/0    Ss   08:24   0:00 bash
root         181  0.0  0.0   7640  2696 pts/0    R+   08:57   0:00 ps aux

I started/stopped the container, deleted it and recreated it, still not listening. I guess a process is not starting in the container ?
I also tried image jc21/nginx-proxy-manager: 2.10.3 but got the same.
Help would be apreciated.
Thanks.

[c3h5o9n]

I'm replying to myself.
After a long time it is working, here are the logs:

❯ Configuring npm user ...
❯ Configuring npm group ...
❯ Checking paths ...
❯ Setting ownership ...
❯ Dynamic resolvers ...
❯ IPv6 ...
Enabling IPV6 in hosts in: /etc/nginx/conf.d
- /etc/nginx/conf.d/production.conf
- /etc/nginx/conf.d/default.conf
- /etc/nginx/conf.d/include/assets.conf
- /etc/nginx/conf.d/include/ssl-ciphers.conf
- /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- /etc/nginx/conf.d/include/block-exploits.conf
- /etc/nginx/conf.d/include/ip_ranges.conf
- /etc/nginx/conf.d/include/proxy.conf
- /etc/nginx/conf.d/include/force-ssl.conf
- /etc/nginx/conf.d/include/resolvers.conf
Enabling IPV6 in hosts in: /data/nginx
- /data/nginx/proxy_host/1.conf
❯ Docker secrets ...

-------------------------------------
 _   _ ____  __  __
| \ | |  _ \|  \/  |
|  \| | |_) | |\/| |
| |\  |  __/| |  | |
|_| \_|_|   |_|  |_|
-------------------------------------
User:  npm PUID:0 ID:0 GROUP:0
Group: npm PGID:0 ID:0
-------------------------------------

❯ Starting backend ...
❯ Starting nginx ...
[11/27/2023] [10:02:20 AM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
[11/27/2023] [10:02:22 AM] [Migrate  ] › ℹ  info      Current database version: none
[11/27/2023] [10:02:23 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[11/27/2023] [10:02:24 AM] [Setup    ] › ℹ  info      Logrotate completed.
[11/27/2023] [10:02:24 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[11/27/2023] [10:02:24 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[11/27/2023] [10:02:24 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[11/27/2023] [10:02:24 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[11/27/2023] [10:02:24 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[11/27/2023] [10:02:24 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[11/27/2023] [10:02:24 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[11/27/2023] [10:02:24 AM] [Global   ] › ℹ  info      Backend PID 191 listening on port 3000 ...
[11/27/2023] [10:02:25 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[11/27/2023] [10:02:25 AM] [SSL      ] › ℹ  info      Renew Complete

It seems container was stuck after Setting ownerships.
Is there a way to speed up the up process, especially around network ? disabling ipv6 ? where are dynmaic resolvers configured ?
Because It takes so many time to start that I got time to configure traefik to have a look at it ...