You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running Watchtower on ARM 64 Raspbian, has been working ever since and stopped now with the following error message:
Could not do a head request for "sha256:e1688bbea26473c306345275b9b1f2ccad6c9293af9298d28098c629a77fcbf6", falling back to regular pull.
Reason: registry responded to head request with "401 Unauthorized", auth: "Bearer realm=\"https://auth.docker.io/token\",service=\"registry.docker.io\",scope=\"repository:library/sha256:pull\",error=\"insufficient_scope\""
Unable to update container "/watchtower": Error response from daemon: pull access denied for sha256, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. Proceeding to next.
nothing was changed in the config and i do run watchtower every 5 days, so pull request shouldn't be an issue
anyone having or had that issue and knows what to do?
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! 🙏
The actual error is that the image name is just a hash (sha256:e1688bbea26473c306345275b9b1f2ccad6c9293af9298d28098c629a77fcbf) which means that watchtower cannot update it. See #1050
The actual error is that the image name is just a hash (sha256:e1688bbea26473c306345275b9b1f2ccad6c9293af9298d28098c629a77fcbf) which means that watchtower cannot update it. See #1050
can't run "latest-dev" as it is only available for amd64 for now, but ill watch #1050
thanks
Running Watchtower on ARM 64 Raspbian, has been working ever since and stopped now with the following error message:
nothing was changed in the config and i do run watchtower every 5 days, so pull request shouldn't be an issue
anyone having or had that issue and knows what to do?
watchtower config:
The text was updated successfully, but these errors were encountered: