What causes "denied: requested access to the resource is denied"?

Image not tagged with your Docker Hub username or organization namespace Not logged in to Docker Hub or the target registry Docker login session expired or credentials corrupted in ~/.docker/config.json

How to fix denied: requested access to the resource is denied in Docker

DockerBEGINNERMEDIUMUpdated Dec 6, 2025· 261 views

The 'denied: requested access to the resource is denied' error occurs when Docker cannot authenticate or authorize access to a container registry. This typically happens when pushing images without proper tagging, missing authentication, or insufficient permissions on the target repository.

Quick fix

Fixes denied: requested access to the resource is denied

# Check your current image tags
docker images

# If your image is tagged as 'myapp:latest' without a username, retag it:
docker tag myapp:latest YOUR_DOCKERHUB_USERNAME/myapp:latest

# Verify the new tag
docker images | grep myapp

Verify your image tag includes your username
Log in to Docker Hub
Reset credentials and log in fresh
Verify Docker Hub email confirmation

docker — error

$# Check your current image tags
docker images
# If your image is tagged as 'myapp:latest' without a username, retag it:
docker tag myapp:latest YOUR_DOCKERHUB_USERNAME/myapp:latest
# Verify the new tag
docker images | grep myapp
denied: requested access to the resource is denied

What this error means

This error appears when Docker attempts to access a container registry (such as Docker Hub, GitHub Container Registry, or Amazon ECR) but the request is rejected due to authentication or authorization issues. The registry is essentially saying "I do not recognize you as someone who has permission to access this resource." This can happen during both push and pull operations, though it is most commonly encountered when pushing images. There are three main categories of causes: 1. **Authentication issues** - You are not logged in, your session has expired, or your credentials are corrupted 2. **Authorization issues** - You are logged in but do not have permission to access the specific repository 3. **Naming issues** - The image is not tagged correctly to match your account or the repository does not exist

Typical symptoms

Docker push fails immediately with 'denied: requested access to the resource is denied'
Docker pull fails for private images with access denied message
CI/CD pipelines fail at the container registry step
Error appears after successful docker build
Login seems successful but push/pull still fails
Works locally but fails in CI environment
Error occurs only for specific images or repositories

Common causes

Image not tagged with your Docker Hub username or organization namespace
Not logged in to Docker Hub or the target registry
Docker login session expired or credentials corrupted in ~/.docker/config.json
Trying to push to a repository owned by another user or organization
Email address not verified on Docker Hub account
Exceeded private repository limit on Docker Hub free tier
Inconsistent use of sudo between login and push commands
Repository does not exist and auto-creation is disabled
Wrong registry URL used for login vs push
Personal Access Token missing required scopes for private registry

How to fix "denied: requested access to the resource is denied"

1Verify your image tag includes your username

The most common cause is an incorrectly tagged image. Docker Hub requires images to follow the format username/image:tag.

bash

# Check your current image tags
docker images

# If your image is tagged as 'myapp:latest' without a username, retag it:
docker tag myapp:latest YOUR_DOCKERHUB_USERNAME/myapp:latest

# Verify the new tag
docker images | grep myapp

Replace YOUR_DOCKERHUB_USERNAME with your actual Docker Hub username. Find your username at [hub.docker.com](https://hub.docker.com) after logging in.

2Log in to Docker Hub

Ensure you are authenticated with Docker Hub:

bash

# Log in interactively
docker login

# For CI/CD, use stdin to avoid exposing credentials
echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin

After successful login, you should see "Login Succeeded". Credentials are stored in ~/.docker/config.json.

3Reset credentials and log in fresh

If login appears successful but push still fails, your cached credentials may be corrupted:

bash

# Log out from Docker Hub
docker logout

# Remove cached credentials
rm ~/.docker/config.json

# Log in again
docker login

On Windows, the config file is at C:\Users\<username>\.docker\config.json. On macOS, credentials may also be stored in Keychain.

4Verify Docker Hub email confirmation

Docker Hub requires email verification before you can push images:

1. Go to [hub.docker.com](https://hub.docker.com) and log in
2. Click on your profile icon and select "Account Settings"
3. Check if your email is verified
4. If not, click "Resend verification email"
5. Click the link in the verification email
6. Retry your docker push command

5Check repository permissions

If pushing to an organization repository, verify you have push access:

1. Go to the repository page on Docker Hub
2. Click "Settings" then "Permissions"
3. Verify your account has "Write" or "Admin" access
4. If not, ask the organization owner to grant access

For your own repositories, ensure the repository name matches your username exactly (case-sensitive).

6Push the correctly tagged image

After fixing the authentication and tagging, push your image:

bash

# Push to Docker Hub
docker push YOUR_DOCKERHUB_USERNAME/myapp:latest

# For organizations
docker push YOUR_ORG_NAME/myapp:latest

You should see layer upload progress. If it fails immediately, check the error message for clues.

Advanced notes

### Private Registry Authentication

For private registries (not Docker Hub), include the registry URL in both login and tag:

bash

# Log in to private registry
docker login registry.example.com

# Tag with registry URL
docker tag myapp:latest registry.example.com/myapp:latest

# Push
docker push registry.example.com/myapp:latest

### GitHub Container Registry (GHCR)

GHCR requires a Personal Access Token (PAT) with write:packages scope:

bash

echo $GITHUB_PAT | docker login ghcr.io -u USERNAME --password-stdin
docker tag myapp:latest ghcr.io/USERNAME/myapp:latest
docker push ghcr.io/USERNAME/myapp:latest

### Amazon ECR

Authenticate using AWS CLI:

bash

aws ecr get-login-password --region us-east-1 | \
  docker login --username AWS --password-stdin \
  123456789012.dkr.ecr.us-east-1.amazonaws.com

### Sudo Credential Scope

Credentials are stored per-user. Using sudo changes which credentials Docker uses:

bash

# Regular user credentials
docker login        # Stores in ~/.docker/config.json
docker push myimage # Uses ~/.docker/config.json

# Root credentials
sudo docker login   # Stores in /root/.docker/config.json
sudo docker push    # Uses /root/.docker/config.json

Be consistent: if you use sudo docker push, you must also use sudo docker login.

### Docker Hub Rate Limits and Repository Limits

Free Docker Hub accounts have limits:
- Private repositories: Limited to 1 (as of 2023)
- Pull rate limits: 100 pulls per 6 hours for anonymous, 200 for authenticated

If you exceed private repo limits, pushes may fail with access denied. Check your limits at hub.docker.com account settings.

### CI/CD Best Practices

For CI/CD pipelines:

yaml

# GitHub Actions example
- name: Login to Docker Hub
  uses: docker/login-action@v3
  with:
    username: ${{ secrets.DOCKERHUB_USERNAME }}
    password: ${{ secrets.DOCKERHUB_TOKEN }}

Use Docker Hub Access Tokens instead of passwords for better security and easier revocation.

Frequently asked questions

What does "denied: requested access to the resource is denied" mean?: This error appears when Docker attempts to access a container registry (such as Docker Hub, GitHub Container Registry, or Amazon ECR) but the request is rejected due to authentication or authorization issues. " This can happen during both push and pull operations, though it is most commonly encountered when pushing images. There are three main categories of causes: 1.
How do I fix "denied: requested access to the resource is denied"?: The 'denied: requested access to the resource is denied' error occurs when Docker cannot authenticate or authorize access to a container registry. This typically happens when pushing images without proper tagging, missing authentication, or insufficient permissions on the target repository.
What causes "denied: requested access to the resource is denied"?: Image not tagged with your Docker Hub username or organization namespace Not logged in to Docker Hub or the target registry Docker login session expired or credentials corrupted in ~/.docker/config.json
Is the "denied: requested access to the resource is denied" error serious?: It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading

📚Docker Official Documentation
💬
Stack Overflow - Docker push denied(Stack Overflow)
📖
Docker Docs - Build, tag, and publish an image(Official Docs)
📖
Docker Docs - docker image push(Official Docs)
💬
Docker Forums - Push error discussion(Stack Overflow)
🐙
GitHub Issue - push fails denied access(GitHub)
📝
Dev.to - 100 Common Docker Errors

How to fix denied: requested access to the resource is denied in Docker

Quick fix

What this error means

Typical symptoms

Common causes

How to fix "denied: requested access to the resource is denied"

Advanced notes

Frequently asked questions

Related errors

Official resources & further reading