Could not do a head request for .........

[n0rt0nthec4t]

Could not do a head request for .........

[redstormsju]

I just got this error as well..
Could not do a head request for "cloudflare/cloudflared:latest", falling back to regular pull.
Reason: Get "https://index.docker.io/v2/": dial tcp: lookup index.docker.io on 192.168.1.1:53: read udp 172.17.0.5:48571->192.168.1.1:53: i/o timeout
Could not do a head request for "postgres:16", falling back to regular pull.
Reason: Get "https://index.docker.io/v2/": dial tcp: lookup index.docker.io on 192.168.1.1:53: read udp 172.17.0.5:42865->192.168.1.1:53: i/o timeout

[github-actions]

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

[n0rt0nthec4t]

Any movement on this???

[redstormsju]

I tried this….so far haven’t had this message. However I did update container manually before doing this. So we shall see what happens watchtower interval as appropriate. #tips

…

On Thu, Jun 13, 2024 at 8:06 PM mark ***@***.***> wrote: Any movement on this??? — Reply to this email directly, view it on GitHub <#1980 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYOO5PJYCKKK4MX6DHV7VVTZHIXZJAVCNFSM6AAAAABHTH3HZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRWHE4DENZSGA> . You are receiving this because you commented.Message ID: ***@***.***>

[apriliars3]

Same issue from yesterday. only updates every 24 hours.

Could not do a head request for "dgongut/docker-controller-bot:latest", falling back to regular pull.
Reason: invalid character '<' looking for beginning of value
Unable to update container "/docker-controller-bot": Error response from daemon: Head "https://registry-1.docker.io/v2/dgongut/docker-controller-bot/manifests/latest": received unexpected HTTP status: 503 Service Unavailable. Proceeding to next.
Could not do a head request for "portainer/portainer-ce:latest", falling back to regular pull.
Reason: invalid character '<' looking for beginning of value
Unable to update container "/portainer": Error response from daemon: Head "https://registry-1.docker.io/v2/portainer/portainer-ce/manifests/latest": received unexpected HTTP status: 503 Service Unavailable. Proceeding to next.
Could not do a head request for "portainer/agent:latest", falling back to regular pull.
Reason: invalid character '<' looking for beginning of value
Unable to update container "/portainer_agent": Error response from daemon: Head "https://registry-1.docker.io/v2/portainer/agent/manifests/latest": received unexpected HTTP status: 503 Service Unavailable. Proceeding to next.
Could not do a head request for "jsavargas/telethon_downloader:latest", falling back to regular pull.
Reason: invalid character '<' looking for beginning of value
Unable to update container "/telethon_downloader": Error response from daemon: Head "https://registry-1.docker.io/v2/jsavargas/telethon_downloader/manifests/latest": received unexpected HTTP status: 503 Service Unavailable. Proceeding to next.
Could not do a head request for "kostyaesmukov/smtp_to_telegram:latest", falling back to regular pull.
Reason: invalid character '<' looking for beginning of value
Unable to update container "/smtp_to_telegram": Error response from daemon: Head "https://registry-1.docker.io/v2/kostyaesmukov/smtp_to_telegram/manifests/latest": received unexpected HTTP status: 503 Service Unavailable. Proceeding to next.
Could not do a head request for "containrrr/watchtower:latest", falling back to regular pull.
Reason: invalid character '<' looking for beginning of value
Unable to update container "/watchtower": Error response from daemon: Head "https://registry-1.docker.io/v2/containrrr/watchtower/manifests/latest": received unexpected HTTP status: 503 Service Unavailable. Proceeding to next.

[Triarii1]

The issue seems to remain as I keep getting these for example:

level=warning msg="Could not do a head request for "tailscale/tailscale:latest", falling back to regular pull." container=/tailscale image="tailscale/tailscale:latest"
level=warning msg="Reason: Get "https://index.docker.io/v2/\": dial tcp: lookup index.docker.io on 127.0.0.11:53: server misbehaving" container=/tailscale image="tailscale/tailscale:latest"
level=warning msg="Could not do a head request for "pihole/pihole:latest", falling back to regular pull." container=/pihole image="pihole/pihole:latest"

[Hero9909]

we got here after reconfiguration of the watchtower, we changed our config to do 12h checks. i suspected that we hit ratelimits on docker.io, until i found this issue here.