-
Notifications
You must be signed in to change notification settings - Fork 861
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
Container does not get updated #1999
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! 🙏 |
I have a similar issue. This is the configuration I am using: These are the logs: There's a specific message regarding authentication, but I made sure I am using a current and valid docker token:
} I am using for all my docker images the platform tag for x64. I don't know if that is that is the root cause of the issue, but I doubt it. Additionally, watchtower was working fine up until a month ago. I haven't changed nothing in the meantime. Is there a chance someone can help? Thank you in advance for your help. |
Anyone? Please help! |
Since las 2-3 month I think, container images are not getting updated. Checking the logs I see that watchtower is detecting same image hash, somehow it is not getting the new image hash from index.docker.io. I have been checking the images in the docker hub and they have been updated, watchtowerr is not getting that info and new hash. Here are some logs:
|
Unfortunately, I meeted the same issue.
|
You had one job 🙄 |
Apologies. I haven't been able to reproduce the error since I enabled debug
logging. Will do as soon as it happens again
…On Sat, 31 Aug 2024, 16:42 Lewis Dexter Litanzios, ***@***.***> wrote:
You had one job 🙄
—
Reply to this email directly, view it on GitHub
<#1999 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJSISCCAN774OLQYVLYNGTZUHP4RAVCNFSM6AAAAABK24GRN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRSHEZTQMJSGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I encountered this issue today with Watchtower version 1.7.1. Similar relevant logs, where the digests do not match between local and remote, but Watchtower is unable to find new images after a subsequent pull. I've had to redact the image and organization names.
|
Describe the bug
When the image of a docker compose service is updated, it gets pulled, but the docker container does not get recreated or stopped. I'm not sure if it's related to compose.
Steps to reproduce
Expected behavior
The container stops and gets recreated with the latest image
Screenshots
No response
Environment
Your logs
Additional context
No response
The text was updated successfully, but these errors were encountered: