[GH-ISSUE #993] fatal: unable to exec run: Permission denied #832

Closed
opened 2026-02-26 06:34:36 +03:00 by kerem · 1 comment
Owner

Originally created by @JohnGalt1717 on GitHub (Apr 1, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/993

Describe the bug
Hi, I'm getting this in the logs when I start up:

s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise nginx: warning: unable to spawn ./run - waiting 10 seconds

Here's the command to start:

podman run -d --network proxy --restart always --name npm -e TZ="America/New_York" -v "/mnt/data/proxy/data:/data" -v "/mnt/data/proxy/letsencrypt:/etc/letsencrypt" -e DB_SQLITE_FILE="/data/database.sqlite" --privileged jc21/nginx-proxy-manager:latest

Directories have full permissions and container can write to the /data folder.

Expected behavior
Should start normally.

Operating System

  • Debian ARM64.

Additional context
Unifi Dream Machine Pro

Originally created by @JohnGalt1717 on GitHub (Apr 1, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/993 **Describe the bug** Hi, I'm getting this in the logs when I start up: s6-supervise (child): fatal: unable to exec run: Permission denied s6-supervise nginx: warning: unable to spawn ./run - waiting 10 seconds Here's the command to start: podman run -d --network proxy --restart always --name npm -e TZ="America/New_York" -v "/mnt/data/proxy/data:/data" -v "/mnt/data/proxy/letsencrypt:/etc/letsencrypt" -e DB_SQLITE_FILE="/data/database.sqlite" --privileged jc21/nginx-proxy-manager:latest Directories have full permissions and container can write to the /data folder. **Expected behavior** Should start normally. **Operating System** - Debian ARM64. **Additional context** Unifi Dream Machine Pro
kerem 2026-02-26 06:34:36 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@renedis commented on GitHub (Apr 5, 2021):

This is an issue with systemd and podman.

Solve it by adding:
--systemd=false

Not NPM related

<!-- gh-comment-id:813395857 --> @renedis commented on GitHub (Apr 5, 2021): This is an issue with systemd and podman. Solve it by adding: --systemd=false Not NPM related
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#832
No description provided.