ProjectStack
docker

Error response from daemon: manifest for X:Y not found: manifest unknown: manifest unknown

The image exists on the registry, but the specific tag you requested doesn't. Docker uses image manifests to describe each version, and a 'manifest unknown' error means no manifest was found for that tag — usually because the tag is misspelled or doesn't exist yet.

Common causes

  • The tag name is misspelled — check exact casing and spelling on Docker Hub
  • The tag hasn't been pushed yet — the image exists but this version hasn't been published
  • You're referencing a tag from a different registry or repository than you think
  • The tag was deleted or renamed on the registry

How to fix it

  1. Check available tags on Docker Hub: visit hub.docker.com and browse the image's Tags tab
  2. Use the docker manifest inspect command to see what tags are available: docker manifest inspect image:tag
  3. Pull a known stable tag like :latest or a version you know exists: docker pull nginx:stable
  4. If building your own image, push it first before trying to pull: docker push myrepo/myimage:v1

Example

$ docker pull node:18-alpin Error response from daemon: manifest for node:18-alpin not found: manifest unknown: manifest unknown

Typo in the tag — 18-alpin instead of 18-alpine — the correct tag doesn't exist

Related Docker Errors

Cannot connect to Docker daemonPermission denied connecting to Docker socketDocker daemon not running on this hostImage not found or pull access deniedUnauthorized — authentication required

Browse more errors

The Developer Hub covers 150+ errors across Git, npm, Node.js, Python, TypeScript, and Docker — with plain-English explanations and fix steps.