Skip to content
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

Containers from other registries stop updating if docker.io is inaccessible #2051

Open
KostyaLocal opened this issue Nov 13, 2024 · 2 comments

Comments

@KostyaLocal
Copy link

KostyaLocal commented Nov 13, 2024

Describe the bug

The update stops working if there are problems accessing docker.io.
Containers from other registries also stop updating

Steps to reproduce

Don't know how to reproduce

Expected behavior

The update continues to work for available registries

Screenshots

No response

Environment

  • Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-48-generic x86_64)
    Docker version 27.3.1, build ce12230

Your logs

time="2024-11-13T20:20:14Z" level=warning msg="Could not do a head request for \"containrrr/watchtower:latest\", falling back to regular pull." container=/watchtower image="containrrr/watchtower:latest"
time="2024-11-13T20:20:14Z" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": read tcp 172.17.0.7:36730->54.198.86.24:443: read: connection timed out" container=/watchtower image="containrrr/watchtower:latest"

Additional context

No response

Copy link

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! 🙏

@prohand
Copy link

prohand commented Dec 20, 2024

Hello,

Same problem, do you have a solution ?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants