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

[n0rt0nthec4t]

Describe the bug

Seems recently been getting these errors/warnings popping up in my watchtower logs. never seen before. Not sure what this all means

Steps to reproduce

.Appearing in logs

Expected behavior

No warnings?

Screenshots

No response

Environment

Docker version 26.1.2, build 211e74b
Ubuntu 24.04 x64

Your logs

time="2024-05-13T09:57:29+10:00" level=warning msg="Could not do a head request for \"portainer/portainer-ce:latest\", falling back to regular pull." container=/portainer image="portainer/portainer-ce:latest"
time="2024-05-13T09:57:29+10:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": dial tcp: lookup index.docker.io on x.x.x.x:53: read udp y.y.y.y:49510->x.x.x.x:53: i/o timeout" container=/portainer image="portainer/portainer-ce:latest"

Additional context

No response

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

[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

[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"

[Nebdir]

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.

[xiaozhubin]

same question since Sept 12

[KingDoum]

me too

[n0rt0nthec4t]

Guess it'll never get fixed since being raised 5months ago

[EDIflyer]

Everything working fine for the past couple of years but seeing lots more of these errors recently - anyone worked out what is going on?

Could not do a head request for "matomo:latest", falling back to regular pull.
Reason: invalid character '<' looking for beginning of value
Found new typhonragewind/meshcentral:latest image (221b58c908f7)
Could not do a head request for "jc21/nginx-proxy-manager:github-pr-3121", falling back to regular pull.
Reason: registry responded to head request with "404 Not Found", auth: "not present"
Unable to update container "/nginx-proxy-manager-app-1": Error response from daemon: manifest for jc21/nginx-proxy-manager:github-pr-3121 not found: manifest unknown: manifest unknown. Proceeding to next.

[xiaozhubin]

I got the same wrong message when I run docker compose in cmd.
I find this https://forums.docker.com.
Then I logged in my account in docker.com, then create a Personal access tokens in account setting, and run the command line it tells, then the docker compose in command line worked.
It seems docker.com change something, you have to log in to use the service.
You guys can try it.

[EDIflyer]

Interesting, thanks @xiaozhubin - have created a token and logged in via the CLI, so will see if that makes a difference.

[EDIflyer]

Just to update - no change overnight despite the PAT being in place.

[n0rt0nthec4t]

I'm getting the impression this project is not being maintained anymore? Over 12 months since the last release etc etc

[xiaozhubin]

Just to update - no change overnight despite the PAT being in place.

me neither ☹️

[johnny-de]

I'm experiencing a similar issue with log warnings during container updates.

time="2024-11-04T20:57:32Z" level=warning msg="Could not do a head request for \"nodered/node-red:latest\", falling back to regular pull." container=/nodered_18 image="nodered/node-red:latest"
time="2024-11-04T20:57:32Z" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": dial tcp: lookup index.docker.io on 192.168.0.10:53: dial udp 192.168.0.10:53: connect: network is unreachable" container=/nodered_18 image="nodered/node-red:latest"
time="2024-11-04T20:57:33Z" level=warning msg="Could not do a head request for \"louislam/uptime-kuma:latest\", falling back to regular pull." container=/uptimekuma_7 image="louislam/uptime-kuma:latest"

Despite these warnings, the containers appear to update successfully.

time="2024-11-01T20:57:36Z" level=info msg="Stopping /changedetectionio_17 (ad5d26b9c1dd) with SIGTERM"
time="2024-11-01T20:57:39Z" level=info msg="Creating /changedetectionio_17"
time="2024-11-01T20:57:40Z" level=info msg="Removing image 0d2e81d50528"
time="2024-11-01T20:57:40Z" level=info msg="Session done" Failed=0 Scanned=17 Updated=1 notify=no