Replies: 1 comment 3 replies
-
The |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I have Watchtower 1.7.1 installed, pushing notifications through Discord. Had been working flawlessly for many months.
I recently updated my Synology DSM, with a full restart of my Docker stack. Everything else seems to be working smoothly, and certainly no changes to my docker-compose file; however, am now getting errors with Watchtower updates:
Unable to update container "/jackett": Error response from daemon: Head "https://ghcr.io/v2/linuxserver/jackett/manifests/latest": dial tcp: lookup ghcr.io on 192.168.1.1:53: no such host. Proceeding to next.
Occurs to multiple containers with a similar "no such host" error etc.
Any idea where the root cause of this is?
My docker-compose config for what it's worth:
Steps to reproduce
Expected behavior
Proper pulls as it was before.
Screenshots
No response
Environment
Your logs
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions