-
-
Notifications
You must be signed in to change notification settings - Fork 38
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 gets a 404 when trying to update #130
Comments
Thanks for opening this issue and looking into it. This does appear to be an issue with watchtower. I did recently update the actions on GitHub because there are phasing out the old actions in May/June which is why we're probably getting this error now. Looks like they have pull request out there to fix the problem, containrrr/watchtower#1526 . I'll monitor it for a few days to see what progress they've made on approving it. For now... docker pull xavierh/goaccess-for-nginxproxymanager:latest will work for you. |
@wrench12435678 can you post a Watchtower debug log snippet, from |
not goaccess image, but technically every image that build using buildx v0.10.0+ will result 404 with watchtower. I saw a PR supporting new OCI manifest containrrr/watchtower#1533 , but cant really tell if it working, as no watchtower development container image to test it out. Ref: |
Try |
That appears to have worked. :) I set the check interval to 10 seconds temporarily. BEFORE
AFTER
|
As Watchtower has fixed the issue on their side (Latest-Dev) and recently have pushed out an update on Latest (Not sure if its part of it), I will close this issue as it's been resolved |
"Could not do a head request for "xavierh/goaccess-for-nginxproxymanager:latest", falling back to regular pull.
Reason: registry responded to head request with "404 Not Found", auth: "not present""
Recently change detection had the same issue with buildx, docker/setup-buildx-action#187
It seems to be related to "provenance: false"
Is this the same issue for go access, or a different reason watchtower is failing to update?
Thanks
The text was updated successfully, but these errors were encountered: