docker image_error ai_generated true

Error response from daemon: manifest for image not found

ID: docker/image-not-found

Also available as: JSON · Markdown
90%Fix Rate
92%Confidence
50Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
24 active

Root Cause

Docker image or tag does not exist in the registry. Could be a typo, wrong tag, private registry auth issue, or architecture mismatch.

generic

Workarounds

  1. 92% success Verify image name and tag are correct — check for typos
    docker search <image_name>
    # Verify the exact image name on Docker Hub or your registry.
    # Common mistakes: 'postgress' vs 'postgres', 'node:18-alpine' vs 'node:18-Alpine'

    Sources: https://hub.docker.com/

  2. 88% success For private images, authenticate to the registry before pull
    # Docker Hub:
    docker login -u <username>
    
    # Private registry:
    docker login registry.example.com
    
    # AWS ECR:
    aws ecr get-login-password | docker login --username AWS --password-stdin <account>.dkr.ecr.<region>.amazonaws.com
    
    # GCR:
    gcloud auth configure-docker

    Sources: https://docs.docker.com/reference/cli/docker/login/

  3. 85% success Check available tags and architectures on the registry
    # List available tags for a Docker Hub image:
    curl -s 'https://hub.docker.com/v2/repositories/library/node/tags/?page_size=20' | jq '.results[].name'
    
    # Check if the tag supports your architecture:
    docker manifest inspect --verbose node:18-alpine | jq '.[].Platform'
    
    # For multi-arch builds, use --platform:
    docker pull --platform linux/amd64 node:18-alpine

    Sources: https://docs.docker.com/reference/cli/docker/manifest/

Dead Ends

Common approaches that don't work:

  1. Repeatedly retrying docker pull without checking the image name 95% fail

    If the image or tag doesn't exist, retries will always fail

Error Chain

Frequently confused with: