docker
registry
ai_generated
true
manifest unknown: manifest unknown
ID: docker/docker-manifest-unknown
88%Fix Rate
90%Confidence
50Evidence
2023-01-01First Seen
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| 27 | active | — | — | — |
Root Cause
The specified image tag or digest does not exist in the registry. The image may have been deleted, the tag misspelled, or the platform architecture not available.
genericWorkarounds
-
90% success Verify the exact image name, tag, and registry URL
Check the registry web UI or use: docker manifest inspect <image>:<tag> to confirm the manifest exists
Sources: https://docs.docker.com/reference/cli/docker/manifest/inspect/
-
85% success Use a specific digest instead of a mutable tag
docker pull image@sha256:<digest> — ensures you get the exact image that was verified to exist
Sources: https://docs.docker.com/engine/reference/commandline/pull/
Dead Ends
Common approaches that don't work:
-
Pulling with --platform flag when the image simply does not exist for that architecture
80% fail
If the image maintainer never published an arm64 variant, no platform flag will make it appear
-
Clearing local Docker cache hoping it will fix the pull
85% fail
The issue is server-side; the manifest genuinely does not exist in the registry
Error Chain
Frequently confused with: