docker pull says the manifest is not found
manifest not foundShort answer
The registry answered, but it has nothing for the exact name, tag or platform you asked for. Ask the registry what it holds with docker buildx imagetools inspect. That shows whether the tag exists and which platforms it has. Then correct the tag, pin a digest, or pass --platform.
Fix it fast
1Find out which cause you have
Inspect the image on the registry without pulling it. If this command fails too, the name or tag is wrong; if it works, read the Platform lines.
docker buildx imagetools inspect myorg/myapp:1.4.22Match what you see, then jump to its fix
- 1
imagetools inspect fails for the tag but works for another oneThe tag does not exist in that repositoryFix - 2
The failing reference has no colon and the repository has no latest tagNo tag was given, so Docker asked for latestFix - 3
The tag exists, but its Manifests list has no entry for your CPU, for example linux/arm64 on an ARM machineThe image has no build for your platformFix
- 1
What does the error look like?
manifest not founddocker pull fails for a tag or platform the registry does not list
Cause 1 of 3
The tag does not exist in that repository
1Check
A pull is NAME:TAG or NAME@DIGEST. A typo, a tag that was never pushed or a tag that was deleted gives no manifest.
docker buildx imagetools inspect myorg/myapp:1.4.2
docker buildx imagetools inspect myorg/myapp:latest2Fix
Use a tag that exists. Check your CI log to confirm the push finished, and fix the tag in your Compose file or Dockerfile.
docker pull myorg/myapp:1.4.13Verify
The pull completes and shows the digest.
docker image ls myorg/myappConfirmed by docs.docker.com
Cause 2 of 3
No tag was given, so Docker asked for latest
1Check
If you leave out the tag, Docker pulls :latest. A repository that only publishes version tags has none.
docker buildx imagetools inspect myorg/myapp2Fix
Write the tag you want, or pin a digest to get exactly one version.
docker pull myorg/myapp:1.4.2
docker pull myorg/myapp@sha256:<digest>3Verify
The pull now resolves.
docker image ls myorg/myappConfirmed by docs.docker.com
Cause 3 of 3
The image has no build for your platform
1Check
A multi-platform tag is a manifest list with one entry per platform. Print the Platform lines and compare them with your host.
docker buildx imagetools inspect myorg/myapp:1.4.2 | grep Platform
uname -m2Fix
Pull an image that has your platform, or ask for the platform that is present with --platform. If you publish the image, build it for each platform you need.
docker pull --platform linux/amd64 myorg/myapp:1.4.23Verify
The pull completes for the platform you chose.
docker image ls myorg/myappConfirmed by docs.docker.com
How do I stop it coming back?
- Pin tags to a version or digest in Compose files and Dockerfiles; avoid depending on latest.
- In CI, run imagetools inspect after a push to prove the tag exists before you deploy.
- Publish multi-platform images when your team uses both x86 and ARM machines.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Servers
Apache logs SIGWINCH and exits on its own
the httpd container stops although nothing crashed
SIGWINCH is Apache's graceful-stop signal.
2 causes, each with a fixServers
sam local fails: Running AWS SAM projects locally requires Docker
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
sam local start-api and sam local invoke run your function inside a Docker container, so SAM stops if it cannot talk to Docker.
3 causes, each with a fixServers
dnf fails to download repo metadata in a CentOS 8 Docker build
The same Dockerfile built fine before 2022
CentOS Linux 8 reached end of life on 31 December 2021 and its content left the mirrors.
2 causes, each with a fixServers
pip install confluent-kafka fails because librdkafka/rdkafka.h is missing
pip stops while building confluent-kafka from source
The error means pip is compiling confluent-kafka from source, and the compiler cannot find the librdkafka C headers.
3 causes, each with a fixServers
Cypress says the npm package is installed but the binary is missing
Cypress binary is missing after npm install in CI or in a Docker build
The npm package is only a launcher.
3 causes, each with a fixServers
A dev container port does not open in the browser when Docker runs on a remote host
If your application only accepts calls from localhost, it will reject connections from published ports
Three things usually break it: the app listens only on localhost inside the container, so published ports are rejected; you open the container port instead of the mapped localhost port VS Code shows; or you changed appPort or a Compose ports list and did not rebuild.
3 causes, each with a fix