Docker "manifest unknown" / "manifest not found" - Fix Missing Tags

The registry has the repository but not the specific tag or digest you asked for. The image name resolves; the reference does not.

What this error means

A pull fails with manifest unknown or manifest for <repo>:<tag> not found. The repository clearly exists (other tags pull fine), but this exact reference does not.

Error response from daemon: manifest for myorg/api:relese-1 not found:
manifest unknown: manifest unknown

Common causes

The tag was never pushed or was a typo

A misspelled tag (relese-1), or a tag your pipeline assumed exists but a previous job failed to push, leaves nothing for the registry to return.

The tag or digest was deleted or retag­ged

Registry retention policies, manual cleanup, or a moved tag can remove the manifest you cached a reference to.

Architecture/variant not present in the manifest list

For a multi-arch tag, the manifest list may exist but lack an entry for your platform, so the resolved per-arch manifest is "unknown".

How to fix it

List the tags that actually exist

Inspect the registry to confirm the reference before pulling.

docker buildx imagetools inspect myorg/api:1.4.2
# or query tags via the registry API / your provider's CLI

Pin to an immutable digest

Reference images by digest so a moved or deleted tag cannot silently break the pull.

docker pull myorg/api@sha256:9f2c...

How to prevent it

• Verify the push succeeded before downstream jobs pull the tag.
• Pin production references by digest, not by a mutable tag.
• Align retention policies with how long your pipelines reference old tags.

Related guides