mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1091] Docker Container can't start #901
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#901
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @d33pjs on GitHub (May 11, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1091
I have trouble with current Docker Images.
sha256:29aa3e4dbb2b1d58fcb69bb4d73745bc20c48ace12e4b9565d359caabbc16dc3 is working as expected:
But this:
sha256:c9e7873e57504243f42daadf4ae43bd6274a6895f9cf7b5315024acf216a8f6e
and this (both pulled the last cpuple of days with "latest" tag)
sha256:ebe0f248625b27f2fced38dee520f1ead5ded7b954dfa8202306d7e5c9f1a0a0
give the following error on "docker-compose up -d":
I think, there are two errors:
libc.musl-x86_64.so.1: cannot open shared object file: No such file or directoryand
./run: line 27: awk: command not foundMy docker-compose.yaml:
@idolpx commented on GitHub (May 26, 2021):
Try this to resolve the first issue. Login to the shell of the container.
sudo docker exec -it nginxprxmgr bashThen install "musl-dev".
apt-get install musl-devThen create a link to it.
ln -s /usr/lib/x86_64-linux-musl/libc.so /lib/libc.musl-x86_64.so.1Then exit and restart the container.
@github-actions[bot] commented on GitHub (Mar 11, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 24, 2025):
Issue was closed due to inactivity.