Registry responded to head request with "404 Not Found"

Hello,

I update my docker containers automatically with watchtower.
Since some days I get notifications on one image that says:

Could not do a head request for "koenkk/zigbee2mqtt:latest", falling back to regular pull.
Reason: registry responded to head request with "404 Not Found", auth: "not present"

What is this error, and how to fix this? Is it a problem with the image from koenkk/zigbee2mqtt or is it a problem with watchtower?
The problem is not only for me there are a lot of people having trouble and nobody knows exactly why this is happening since some days.

Related topics:

Thanks in advance.

1 Like

Same problem here (other images) :cry:

Also encountering this.

http://docker.io/itzg/minecraft-bedrock-server:latest

This image and zigbee2mqtt

I’m also experiencing this issue with zigbee2mqtt and dozzle now. Other images update just fine. Very peculiar.

23-01-2023 5:58:16
time="2023-01-23T05:58:16+01:00" level=warning msg="Could not do a head request for \"amir20/dozzle:latest\", falling back to regular pull." container=/dozzle image="amir20/dozzle:latest"
23-01-2023 5:58:16
time="2023-01-23T05:58:16+01:00" level=warning msg="Reason: registry responded to head request with \"404 Not Found\", auth: \"not present\"" container=/dozzle image="amir20/dozzle:latest"
23-01-2023 5:58:18
time="2023-01-23T05:58:18+01:00" level=warning msg="Could not do a head request for \"koenkk/zigbee2mqtt:latest\", falling back to regular pull." container=/zigbee2mqtt image="koenkk/zigbee2mqtt:latest"
23-01-2023 5:58:18
time="2023-01-23T05:58:18+01:00" level=warning msg="Reason: registry responded to head request with \"404 Not Found\", auth: \"not present\"" container=/zigbee2mqtt image="koenkk/zigbee2mqtt:latest"
23-01-2023 5:58:50
time="2023-01-23T05:58:50+01:00" level=info msg="Session done" Failed=0 Scanned=40 Updated=0 notify=no
23-01-2023 6:58:05
time="2023-01-23T06:58:05+01:00" level=warning msg="Could not do a head request for \"amir20/dozzle:latest\", falling back to regular pull." container=/dozzle image="amir20/dozzle:latest"
23-01-2023 6:58:05
time="2023-01-23T06:58:05+01:00" level=warning msg="Reason: registry responded to head request with \"404 Not Found\", auth: \"not present\"" container=/dozzle image="amir20/dozzle:latest"
23-01-2023 6:58:07
time="2023-01-23T06:58:07+01:00" level=warning msg="Could not do a head request for \"koenkk/zigbee2mqtt:latest\", falling back to regular pull." container=/zigbee2mqtt image="koenkk/zigbee2mqtt:latest

Encountering this as well for some subset of our repos.

Failing manifest queries:

livepeer/data:main
livepeer/go-livepeer:master
livepeer/orch-tester:latest
livepeer/task-runner:main
livepeerci/api:dev
livepeerci/api:master

Successful manifest queries:

grafana/grafana-image-renderer:latest
livepeer/data:dev
livepeer/go-livepeer:yf-sender-nonce-debug
livepeer/lpms-runner:master
livepeer/monitoring:latest
livepeer/monitoring:latest-staging
livepeer/pricing-api:latest
livepeer/record-tester:v0.12.28
livepeer/task-runner:dev
livepeer/webrtmp-server:latest
livepeerci/bgpm:0.6.0
livepeerci/bgpm:0.8.0
livepeerci/catalyst:canary
livepeerci/catalyst:main
livepeerci/kube-nodes-connected:latest
livepeerci/mistserver:static-catalyst-updates-drone-amd64
livepeerci/sthc:1.3.0
livepeerci/stream-monitor:3.3.0

IDGI.

I’ve started having this problem with 2 x containers out of the 30 running.

Netdata and Autoheal are experiencing the same fault.

I’ve tried logging back into Docker Hub via CLI, adding :latest tags to the image in the compose script, but still nothing.

Using Pihole, which uses 1.1.1.1 and 8.8.8.8 as upstream, otherwise no probs with anything else?

Anyone else found a solution?

Cheers!

Hello,

the problem was figured out here: Could not do a head request · Discussion #1529 · containrrr/watchtower · GitHub
It is a problem with the new manifest of docker buildx. You can either disable this warning on watchtower or the maintainers of the images can fix it `docker manifest` does not work with output from buildx v0.10 · Issue #1509 · docker/buildx · GitHub.