starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #3348] Upgrade to latest (2.10.4) prevents docker container from starting - exec /init: exec format error #2252

New issue

Closed

opened 2026-02-26 07:34:44 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:34:44 +03:00

Owner

Originally created by @Lyall1979 on GitHub (Nov 23, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3348

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug
Docker container was updated from 2.10.2 to 2.10.4.
Newly updated container does not run
Logs contain only "exec /init: exec format error" before the container tries to restart (due to restart policy).

Nginx Proxy Manager Version
Unable to get to login page due to error - image used is "latest" (2.10.4)

To Reproduce
Steps to reproduce the behavior:

Deploy latest image over older 2.10.2 version
Investigate why container is no longer running
Find logs and error "exec /init: exec format error"
Revert to 2.10.2 - container is working correctly again
Update to 2.10.3 - container is working correctly again

Expected behavior
Container using 2.10.4 image should operate correctly.

Screenshots
Can provide if required

Operating System
OMV (OpenMediaVault) 6.9.8-1 (Shaitan)
Linux 6.1.0-0.deb11.11-amd64

Additional context
Rolling back to 2.10.3 makes the container function correctly again.

Originally created by @Lyall1979 on GitHub (Nov 23, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3348  **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** Docker container was updated from 2.10.2 to 2.10.4. Newly updated container does not run Logs contain only "exec /init: exec format error" before the container tries to restart (due to restart policy). **Nginx Proxy Manager Version** Unable to get to login page due to error - image used is "latest" (2.10.4) **To Reproduce** Steps to reproduce the behavior: 1. Deploy latest image over older 2.10.2 version 2. Investigate why container is no longer running 3. Find logs and error "exec /init: exec format error" 4. Revert to 2.10.2 - container is working correctly again 5. Update to 2.10.3 - container is working correctly again **Expected behavior** Container using 2.10.4 image should operate correctly. **Screenshots** Can provide if required **Operating System** OMV (OpenMediaVault) 6.9.8-1 (Shaitan) Linux 6.1.0-0.deb11.11-amd64 **Additional context** Rolling back to 2.10.3 makes the container function correctly again.

kerem

2026-02-26 07:34:44 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:34:44 +03:00

Author

Owner

@lorenzopicoli commented on GitHub (Nov 25, 2023):

I also couldn't start the container after 2.10.4. I fixed it like this: https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/3349

@lorenzopicoli commented on GitHub (Nov 25, 2023): I also couldn't start the container after 2.10.4. I fixed it like this: https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/3349

kerem commented

2026-02-26 07:34:44 +03:00

Author

Owner

@Lyall1979 commented on GitHub (Nov 30, 2023):

I also couldn't start the container after 2.10.4. I fixed it like this: #3349

I already had the 'LetEncrypt' volume bound.

@Lyall1979 commented on GitHub (Nov 30, 2023): > I also couldn't start the container after 2.10.4. I fixed it like this: #3349 I already had the 'LetEncrypt' volume bound.

kerem commented

2026-02-26 07:34:44 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 17, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Jul 17, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:34:44 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 8, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Aug 8, 2025): Issue was closed due to inactivity.

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#2252

No description provided.

Rows
Columns