You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running acme.sh as a docker container on my Synology NAS. If I only start a terminal command acme.sh or acme.sh --help, the cursor is blinking and nothing happens. After a few seconds CPU and Memory load runs up until the Diskstation freezes.
Installed via task planer:
docker run -d --name acme.sh \
-v /volume1/docker/acme:/acme.sh \
--net=host \
--restart always \
neilpang/acme.sh:latest daemon
What I found out:
If I remove the volume enviroment it work's. I've checked all required ownerships, they're correct. In terminal I can check nslookup, dns settings, cc., but no acme.sh.
Connecting via ssh terminal@root with docker run --rm -it neilpang/acme.sh /bin/sh, I get a prompt and commands are working (bridge mode, no volumes). Even there, set a volume /docker/acme:/acme.sh leads to the same result.
I stuck since an announced update inside docker to version 3.0.8. Register a new container with separated versions down to 3.0.0 were not successful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm running acme.sh as a docker container on my Synology NAS. If I only start a terminal command
acme.sh
oracme.sh --help
, the cursor is blinking and nothing happens. After a few seconds CPU and Memory load runs up until the Diskstation freezes.Installed via task planer:
What I found out:
If I remove the volume enviroment it work's. I've checked all required ownerships, they're correct. In terminal I can check nslookup, dns settings, cc., but no
acme.sh
.Connecting via ssh terminal@root with
docker run --rm -it neilpang/acme.sh /bin/sh
, I get a prompt and commands are working (bridge mode, no volumes). Even there, set a volume/docker/acme:/acme.sh
leads to the same result.I stuck since an announced update inside docker to version 3.0.8. Register a new container with separated versions down to 3.0.0 were not successful.
Further informations:
Any ideas?
Regards,
Oliver
Beta Was this translation helpful? Give feedback.
All reactions