-
Notifications
You must be signed in to change notification settings - Fork 887
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
error and container crash #740
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! 🙏 |
|
Hm, looks like the |
Sounds like a reasonable assumption. Why, however, is a totally different question. 🤔 |
same here on my synology... anythin I can do as a workaround? |
same here. Then just skipping that update would end up that these containers are never getting updated in the future? |
Could be! However, if the digest is pinned down, you won't get any updates anyway as it will keep checking against that very exact commit. My immediate question is; do you have docker swarm enabled? If so, would you mind turning it off and see if it makes a difference? We've seen this implicit pinning behavior with swarm users previously for some reason. |
Today i checked my watchtower logs and saw the exact same error message.
With a google search I could luckily find out that the sha256 value 5121527e11b8d8652f... belongs to the portainer 2.6.3 image. After I pulled the portainer/portainer-ce:2.6.3 image, watchtower luckily ran again :) i have no idea what exactly bothered watchtower. But at least this is a functional workaround. |
Sorry. completely forgot about this issue. Also because i mainly started managing the containers a bit differently. To answer the question from @simskij . No i am not using Docker Swarm. Its a default docker install on my Synology NAS. So that should not be the issue. |
got this error when using the command docker run --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once
The text was updated successfully, but these errors were encountered: