ProjectStack
docker

Error response from daemon: pull access denied for X, repository does not exist or may require 'docker login'

Docker couldn't pull the image you requested. Either the image name or tag is wrong, the image is in a private registry you aren't logged in to, or the image genuinely doesn't exist on Docker Hub or your configured registry.

Common causes

  • Typo in the image name or tag — Docker Hub and registries are case-sensitive
  • The image is private and you aren't logged in: run docker login first
  • The image uses a different registry (like ghcr.io or ECR) that needs separate authentication
  • The image or tag was deleted or never existed on the specified registry

How to fix it

  1. Double-check the image name and tag: docker pull nginx:1.25 — search Docker Hub to verify
  2. Log in to Docker Hub: docker login, then retry the pull
  3. For private registries: docker login registry.example.com, then pull with the full path
  4. If the image is from another registry, include the full registry URL: docker pull ghcr.io/owner/image:tag

Example

$ docker pull myapp:latest Error response from daemon: pull access denied for myapp, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Pulling a private image from Docker Hub without being logged in

Related Docker Errors

Cannot connect to Docker daemonPermission denied connecting to Docker socketDocker daemon not running on this hostImage manifest not found (tag doesn't exist)Unauthorized — 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.