-
Notifications
You must be signed in to change notification settings - Fork 854
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
Watchtower causes a cron crash on Ubuntu when checking for updates #1026
Comments
Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏 |
So the issue here was a non-referenced image in one of my running containers. Is there a way that watchtower can overcome this issue in the future? If a referenced image doesn't exist, just skip the container instead of crashing the cron task, as in my case, watchtower never ran again until it was manually restarted... Thanks |
Hm, yeah, the sanity check for missing configuration is done after |
To avoid important communication to get lost in a closed issues no one monitors, I'll go ahead and lock this issue. If you want to continue the discussion, please open a new issue. Thank you! 🙏🏼 |
When watchtower runs to check for updates, I receive the following errors in my log, which seems to have two problems:
The first seems similar to Issue #215, however this is running on Ubuntu, not Synology.
The 2nd and more major issue is that there is a crash upon checking for an update for various containers..
How can I address/fix these issues?
Watchtower used to update all my containers correctly, but sometime recently has stopped working.
I've tried:
"sudo docker images --digest --all" to find the image listed in the log, to no avail
"sudo docker image prune -a" to delete the offending image (even though it wasn't listed) to no avail
Stopping all containers except for watchtower and portainer, and portainer was updated successfully.
I've tried adding the "--include-stopped & --revive-stopped" command line switches to update stopped containers and still receive the same crash.
It's not always the same container that the crash happens directly after. I've seen it crash right after gaps, netdata and portainer
Can someone help me out please?
Thanks
The text was updated successfully, but these errors were encountered: