Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Servers, nginx and Docker

docker pull says the manifest is not found

Errormanifest not found

Short 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.

  • Applies to Docker Engine 28, Docker Buildx, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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.2
  2. 2Match what you see, then jump to its fix

    1. 1imagetools inspect fails for the tag but works for another oneThe tag does not exist in that repositoryFix
    2. 2The failing reference has no colon and the repository has no latest tagNo tag was given, so Docker asked for latestFix
    3. 3The 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

What does the error look like?

  • manifest not found
  • docker 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:latest

2Fix

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.1

3Verify

The pull completes and shows the digest.

docker image ls myorg/myapp

Confirmed by docs.docker.com

Did this fix it?

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/myapp

2Fix

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/myapp

Confirmed by docs.docker.com

Did this fix it?

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 -m

2Fix

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.2

3Verify

The pull completes for the platform you chose.

docker image ls myorg/myapp

Confirmed by docs.docker.com

Did this fix it?

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

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

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.