Docker :latest image hangs on startup in Proxmox VE LXC Container (x86_64)

Hello Nginx Proxy Manager Team,

I am experiencing a startup issue with the current :latest Docker image. The container starts but the application within it never becomes fully operational. This issue occurs on a completely fresh installation within a Proxmox VE LXC container, and an older, pinned version of the image works perfectly.

Environment:

Host OS: Proxmox VE (Virtual Environment)

Guest OS: A fresh Debian/Ubuntu-based LXC container running on Proxmox.

Architecture: x86_64 / AMD64

Docker Version: Installed via standard methods on the guest OS.

The Issue
When using the image: 'jc21/nginx-proxy-manager:latest' tag in a docker-compose.yml file, the container gets stuck during the initial setup phase.

Steps to Reproduce:

Create a fresh LXC container on a Proxmox VE host.

Install Docker and Docker Compose.

Create a docker-compose.yml file with the following content:

YAML

version: '3.8'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '443:443'
- '81:81'
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: "npm"
DB_MYSQL_NAME: "npm"
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
depends_on:
- db

db:
image: 'jc21/mariadb-aria:latest'
restart: unless-stopped
environment:
MYSQL_ROOT_PASSWORD: 'npm'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: 'npm'
MARIADB_AUTO_UPGRADE: '1'
volumes:
- ./mysql:/var/lib/mysql
Create the necessary directories: mkdir ./data ./letsencrypt ./mysql

Run the container: docker-compose up -d

Observed Behavior
The docker-compose ps command shows the container is Up, but the application is unresponsive. The logs show that the startup script hangs after the "Setting ownership" step and never proceeds.

The log output for the app container is minimal and ends here:

❯ Configuring npm user ...
useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.
❯ Configuring npm group ...
❯ Checking paths ...
❯ Setting ownership ...
No further logs appear, and the backend never starts. The admin panel on port 81 is inaccessible.

Furthermore, when trying to stop the container with docker-compose down, the Docker daemon logs show that the container is unresponsive and must be force-killed:
level=info msg="Container failed to exit within 10s of signal 15 - using the force"

Successful Workaround
The issue is completely resolved by pinning the image to an older version. Changing the image tag in the docker-compose.yml file to a specific version works perfectly.

Working configuration:

YAML

...
services:
app:
image: 'jc21/nginx-proxy-manager:2.11.2'
...
With the 2.11.2 tag, the application starts correctly, the logs show a full startup sequence, and the admin panel is accessible.

This suggests a regression or an incompatibility in the current :latest build, specifically when running within a Proxmox LXC environment.

Thank you for your great work on this project. I hope this report helps in identifying the issue.

Reproduce the issue from the docker-compose.yml configuration in a fresh Proxmox VE LXC container, comparing jc21/nginx-proxy-manager:latest with 2.11.2. Start with the app logs around the "Setting ownership" step and Docker daemon shutdown message; done means the latest image completes startup and makes the admin panel on port 81 accessible without force-killing the container.