-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker container fails to start with release v0.107.28 #5711
Comments
Seems to be a limitation of the synology DSM interface, and the container must be completely removed and re-added to pick up the new entrypoint / execution command. |
I'm not running it on DSM and the same problem occurred. docker compose down followed by docker compose up -d did not help. Any other ideas? |
@ovizii you'll need to ensure that your container's execution command is correct. The Dockerfile has changed so now the correct command as reported by DSM/portainer is This means the entrypoint is |
I have the same issue on Synology DSM: What to do? |
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question
Operating system type
Linux, Other (please mention the version in the description)
CPU architecture
AMD64
Installation
Docker
Setup
Other (please mention in the description)
AdGuard Home version
v0.107.28
Description
What did you do?
I am running AGH on my Synology NAS inside a docker container, I'm using the DSM 7.1 docker interface to manage the container. I downloaded the newest release via the
latest
tag from docker hub and reset the container to upgrade. Upon trying to restart the container it exits and respawns immediately, spamming the logs with:[FATAL tini (8)] exec -h failed: No such file or directory
Expected result
Docker container starts after upgrading.
Actual result
Docker container fails to start
Additional information
Running the most recent DSM release for my DS1618+: DSM 7.1.1-42962. DSM indicates the container execution command is
/sbin/tini -- -h 0.0.0.0 -c /opt/adguardhome/conf/AdGuardHome.yaml -w /opt/adguardhome/work --no-check-update
The text was updated successfully, but these errors were encountered: