Unable to Find Docker Image Locally
Fix 'Unable to find image locally' Docker errors when pulling or running images that do not exist on your system or registry.
What Does This Error Mean?
The 'Unable to find image locally' error occurs when you try to run or reference a Docker image that does not exist locally and cannot be pulled from any configured registry. Docker first checks the local image cache, then tries to pull from the configured registries.
Common Causes
Typo in the image name or tag (e.g., 'nginix' instead of 'nginx')
Image tag does not exist on the registry (e.g., 'node:20' but you typed 'node:200')
Not logged into a private registry that contains the image
Network issue preventing Docker from reaching the registry
Image was removed from the registry or is no longer available
Docker Hub pull rate limit exceeded for anonymous users
How to Fix It
Verify the image name and tag
Check Docker Hub or your registry for the correct image name and tag.
# Search Docker Hub for an image docker search nginx # Check if the image and tag exist docker pull nginx:latest # Latest tag docker pull nginx:1.25 # Specific version # List locally available images docker images
Log in to private registries
Authenticate with private registries before pulling images.
# Docker Hub (if using a private repo) docker login # Amazon ECR aws ecr get-login-password | docker login --username AWS --password-stdin <account>.dkr.ecr.<region>.amazonaws.com # GitHub Container Registry echo $GITHUB_TOKEN | docker login ghcr.io --username $USERNAME --password-stdin # GitLab Container Registry docker login registry.gitlab.com -u $USERNAME -p $GITLAB_TOKEN
Check Docker Hub rate limits
Unauthenticated users are limited to 100 pulls per 6 hours. Log in to increase limits.
# Check current pull status
docker hub rate-limit
# Login to increase limits from 100 to 200 pulls/6h
docker login
# Use a mirror registry
echo '{"registry-mirrors": ["https://mirror.gcr.io"]}' > /etc/docker/daemon.json
systemctl restart dockerRelated Tools
Use these tools to debug and fix this error:
Related Errors
Other common errors in this category:
Cannot Connect to Docker Daemon
Fix 'Cannot connect to the Docker daemon' error. Learn how to start Docker Desktop, check daemon status, and resolve permission issues.
Port is Already Allocated (Docker)
Fix 'port is already allocated' Docker error when ports conflict between containers or host processes.
Container Name Is Already in Use (Docker)
Fix 'The container name is already in use by container' Docker error. Learn to remove, rename, or reuse existing containers.
Docker Build Failed Error
Fix Docker build failures caused by invalid Dockerfile syntax, missing files, or build context issues.