docker: Manifest unknown for docker pull docker:*
Hey there,
since your recent docker image push today 14th Dec 6:05 UTC i cannot pull any docker image from the official docker registry.
I tried a docker pull:
docker:27.4.0-dinddocker:27.4.0docker:latestdocker:dind
All these result in a manifest for docker:dind not found: manifest unknown: manifest unknown
I have not modified my docker/daemon.json. My local Docker version is Docker version 27.4.0, build bde2b89 on the latest macOS. This problem also occurs on remote Ubuntu VMs.
I’m sorry if its my mistake, but it seems suspicious that the problem occured just after your image push and has not yet been resolved. (We’re running a ci pipeline every 5 minutes and it first failed at 6:13am UTC this morning.) If you need anything, just let me know.
Thanks for any hint or solution. Cheers Max
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 43
- Comments: 18 (5 by maintainers)
“the one should not release a version on friday evenings.”
OK, team was able to get the list of images affected, and may have found a solution; some manual work is involved, so fixes may roll out over time. I’ll post updates once available.
I think we should keep in mind that most of us are using Docker and Docker Official Images without paying for it… Keep in mind that the teams around such tools are putting a lot of effort in to make such great OSS software available to us. I understand that is might be frustrating to see some CIs failing - but no need for strong words & demands such as in the comments above IMHO… PS: Thanks to everyone working on resolving this for the community!!
for now i’m downgrading to version 26 temporarily pulling
docker:26-dindordocker:26is working for meI can give an intermediate status update from the Slack thread.
Team is still looking. They managed to narrow down the cause of the issue to be related to cross-repo links. The image was pushed successfully (data / blobs are there), but some links were not created after the push, causing it to be producing a 404 for those references. A fix was deployed that should prevent this situation from happening, but won’t automatically apply to content that’s already there, and those parts are really locked down, so no direct access to (manually) correct, so they’re currently checking logs to identify images that are affected (beyond the ones mentioned in this ticket), and to see if there’s ways to correct it. Re-pushing the images (same image, but trigger a push again) may work, but may also be locked down (currently being looked into).
This error started to occur only 4 hours ago since the version
27.4.0was released. No need to downgrade todocker:26-dindbecause the previous versiondocker:27.3.1-dindis also working.So just replace
docker:dindwithdocker:27.3.1-dindtemporarily.Same behavior here, we manged to work arround the issue pointing to this image:
docker pull public.ecr.aws/docker/library/docker:dindEDIT:
docker:27.3.1-dindalso works perfectly, thanks @oxilor