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.
pull access denied forrepository does not exist or may require 'docker login'Unable to find image locallyrequested access to the resource is denied 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
- Check the exact name: docker images / registry UI
- docker login <registry> with an account that has access
- Use the full name including registry and tag
Detailed fix by platform
Docker
- bash
docker login ghcr.io -u USERNAME docker pull ghcr.io/myorg/app:1.4.2
Docker Compose
- bash
services: web: image: myorg/web:latest # or build: . to use a local Dockerfile instead of pulling
How to diagnose
- Name — Exact repo/tag on the registry?
- Login — docker info | grep -i registry; cat ~/.docker/config.json
- 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:
Similar errors
- AADSTS50126 AADSTS50126: Error validating credentials due to invalid username or password
- Atlas: bad auth: Authentication failed MongoServerError: bad auth : Authentication failed. (Atlas user / special characters in password)
- auth/invalid-credential Firebase Auth: auth/invalid-credential (auth/wrong-password, auth/user-not-found, auth/invalid-login-credentials)
Most viewed in Docker
- lookup registry-1.docker.io: no such host dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build
- did not complete successfully failed to solve: process "/bin/sh -c ..." did not complete successfully: exit code: 1
- Client.Timeout exceeded Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded)
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 13 Oct 2026