latest image doesn't start

[htogether]

[cont-init ] 15-install-pkgs.sh: terminated successfully.

[cont-init ] 54-db-upgrade.sh: executing...

[cont-init ] 54-db-upgrade.sh: terminated successfully.

[cont-init ] 55-nginx-proxy-manager.sh: executing...

[cont-init ] 55-nginx-proxy-manager.sh: ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /etc/nginx/conf.d/default.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /etc/nginx/conf.d/include/assets.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /etc/nginx/conf.d/include/block-exploits.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /etc/nginx/conf.d/include/force-ssl.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /etc/nginx/conf.d/include/proxy.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /etc/nginx/conf.d/production.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ Enabling IPV6 in hosts: /config/nginx

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /config/nginx/ip_ranges.conf

[cont-init ] 55-nginx-proxy-manager.sh: ❯ /config/nginx/resolvers.conf

[cont-init ] 55-nginx-proxy-manager.sh: terminated successfully.

[cont-init ] 85-take-config-ownership.sh: executing...

[cont-init ] 85-take-config-ownership.sh: terminated successfully.

[cont-init ] 89-info.sh: executing...

╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮

│                                                                      │

│ Application:           Nginx Proxy Manager                           │

│ Application Version:   2.9.19                                        │

│ Docker Image Version:  23.03.2                                       │

│ Docker Image Platform: linux/arm/v7                                  │

│                                                                      │

╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯

[cont-init ] 89-info.sh: terminated successfully.

[cont-init ] all container initialization scripts executed.

[init ] giving control to process supervisor.

[jlesage]

Please provide more details:

• What device are you using.
• OS of the device.
• How you created the container (your docker run command, compose file, etc).

[htogether]

mycloud ex2100 os5 by using portainer stack services: npm: image: 'jlesage/nginx-proxy-manager:latest' container_name: npm networks:

• default restart: always ports:
• "81:8181"
• "8080:8080"
• "8443:4443" volumes:
• /shares/hd2/docker/npm2:/config:rw environment:
• PUID=1002
• PGID=1002

[jlesage]

So [init ] giving control to process supervisor. is the last message you see in the log ?

Do you see the same behaviour if you run:

docker --rm jlesage/nginx-proxy-manager

[jlesage]

FYI, PUID and PGID are not environment variables used by the container.

[htogether]

So [init ] giving control to process supervisor. is the last message you see in the log ?

Do you see the same behaviour if you run:

docker --rm jlesage/nginx-proxy-manager

same result

[cont-init ] 89-info.sh: terminated successfully.

[cont-init ] all container initialization scripts executed.

[init ] giving control to process supervisor.

[htogether]

Hostname WDMyCloudEX2100 OS Information linux armv7l Kernel Version 4.14.22-armada-18.09.3 Total CPU 2 Total memory 1.1 GB

docker version v20.10.17 portainer version ce 2.17.1

[jlesage]

I cannot reproduce on my side using a Raspberry Pi.

Can you run strace on the cinit process:

strace -f -p <pid of cinit>

[htogether]

I try to run on cli error[0038] error waiting for container: context canceled. checked on portainer(container keep restart) wd os5 does not have strace installed