Home·Error messages

docker · Docker

The message

manifest for myapp:v2 not found: manifest unknown

What it means

The repository was found but the tag is not in it. Unlike pull access denied, this message tells you the name was right, so the tag is all that is left to check — a tag that was deleted or moved, a pipeline that pushed latest but never created v2, or a tag that has no image for your architecture. docker manifest inspect myapp:v2 confirms whether the tag resolves at all and which platforms it carries. Switching to latest to get past it costs you a build that cannot be reproduced, so fix the tag instead.

The fix

docker manifest inspect myapp:v2
Printed by
docker
Docker
12

Docker errors only become readable once you place them in a layer — the client failing to reach the daemon, the registry refusing you, a RUN failing during the build, and a container dying the instant it starts are four different problems — and for the build and run layers the line itself is not the reason: the reason is in the output of the command that was running inside, while the cost of each fix differs by layer too.

Reading an error message

  • Read from the first line down. The lower you go the more it is about the tool’s internals; the cause is usually at the top.
  • If there is a file and a line number, start there — not the top stack frame, but the topmost line that names a file you wrote.
  • Search the message verbatim, but strip your own paths and variable names first; those are what stop the search from matching.
  • The same condition is worded differently across tool versions. If results look wrong, add the version number to the query.
  • Before pasting a fix, check what it throws away. Some of these cannot be undone.

Common questions

Q. What does “manifest for myapp:v2 not found: manifest unknown” mean?

The repository was found but the tag is not in it. Unlike pull access denied, this message tells you the name was right, so the tag is all that is left to check — a tag that was deleted or moved, a pipeline that pushed latest but never created v2, or a tag that has no image for your architecture. docker manifest inspect myapp:v2 confirms whether the tag resolves at all and which platforms it carries. Switching to latest to get past it costs you a build that cannot be reproduced, so fix the tag instead.

Q. How do I fix it?

docker manifest inspect myapp:v2 — before running it, check the explanation above for what this command discards.

Q. Which tool prints this?

docker. It sits under Docker, and the message runs to 7 words.

Errors nearby