Common causes
- You haven't run docker login for the registry you're accessing
- Your login session expired — Docker credentials in ~/.docker/config.json are stale
- You're logged in to Docker Hub but the image is on a different registry
- CI/CD pipeline doesn't have the registry credentials configured
How to fix it
- Log in to Docker Hub: docker login with your username and password (or Personal Access Token)
- Log in to a specific registry: docker login registry.example.com
- For GitHub Container Registry: docker login ghcr.io -u USERNAME --password-stdin <<< TOKEN
- In CI/CD, use environment variables for credentials: echo $REGISTRY_TOKEN | docker login -u $REGISTRY_USER --password-stdin
Example
$ docker pull registry.example.com/myapp:latest
Error response from daemon: unauthorized: authentication requiredPulling from a private registry without having logged in first
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.
