pull access denied Docker Origin: Platform & cloud OSI layer 7 · Application Last updated 13 Oct 2026

pull access denied for image, repository does not exist or may require 'docker login'

Docker couldn’t pull the image: the name or tag is wrong, the repository is private and you’re not logged in, or it doesn’t exist on that registry.

Exact message you may see pull access denied forrepository does not exist or may require 'docker login'Unable to find image locallyrequested access to the resource is denied
Seen on: Docker

Meaning

Docker says the same thing for “doesn’t exist” and “not allowed” so it doesn’t leak private repo names. Usually the image name has a typo, is missing the registry/namespace prefix (myorg/app, ghcr.io/org/app), or you built the image locally under a different name and Docker is trying Docker Hub.

Common causes

  • Typo in image name or tag
  • Private repository and not logged in (or logged in to a different registry)
  • Missing registry prefix (ghcr.io/…, 123.dkr.ecr…/…) so Docker Hub is tried
  • Local image built with a different name/tag
  • Image deleted or never pushed

⚡ Quick fix

  1. Check the exact name: docker images / registry UI
  2. docker login <registry> with an account that has access
  3. Use the full name including registry and tag

Detailed fix by platform

Docker

  1. bash
    docker login ghcr.io -u USERNAME
    docker pull ghcr.io/myorg/app:1.4.2

Docker Compose

  1. bash
    services:
      web:
        image: myorg/web:latest   # or build: . to use a local Dockerfile instead of pulling

How to diagnose

  1. Name — Exact repo/tag on the registry?
  2. Login — docker info | grep -i registry; cat ~/.docker/config.json
  3. Local — docker images | grep app

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

AADSTS50126 — AADSTS50126: Error validating credentials due to invalid username or password (Azure)AADSTS50126Atlas: bad auth: Authentication failed — MongoServerError: bad auth : Authentication failed. (Atlas user / special characters in password) (MongoDB)Atlas: bad auth: Auth…auth/invalid-credential — Firebase Auth: auth/invalid-credential (auth/wrong-password, auth/user-not-found, auth/invalid-login-credentials) (Authentication)auth/invalid-credenti…bad auth : Authentication failed — MongoDB: MongoServerError: bad auth : Authentication failed (code 8000 / 18) (MongoDB)bad auth : Authentica…Could not load the default credentials — Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started (Google Cloud / Firebase)Could not load the de…DefaultAzureCredential failed — DefaultAzureCredential failed to retrieve a token from the included credentials / ManagedIdentityCredential authentication unavailable (Azure)DefaultAzureCredentia…denied — denied: requested access to the resource is denied (docker push) (Docker)denieddocker-credential-desktop — error getting credentials - err: exec: "docker-credential-desktop": executable file not found in $PATH (Docker)docker-credential-des…pull acce…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.