How to fix Docker image not found, manifest not found 404 in Kubernetes

KubernetesBEGINNERMEDIUMUpdated Dec 6, 2025· 92 views

Container image specified in pod doesn't exist in registry. Fix by verifying image name, checking registry, and using correct image references.

Quick fix

Fixes IMAGE_NOT_FOUND

kubectl get pod -n <namespace> <pod-name> -o jsonpath='{.spec.containers[0].image}'
  1. Check image reference
  2. Verify image exists
  3. Check registry path
  4. Update deployment with correct image
kubernetes — error
kubectl get pod -n <namespace> <pod-name> -o jsonpath='{.spec.containers[0].image}'
Docker image not found, manifest not found 404

What this error means

When Kubernetes tries to pull a container image, the registry returns 404 (not found). This means the image name, tag, or registry path is incorrect or the image was deleted.

Typical symptoms

  • Pod shows ErrImagePull status
  • kubelet logs show 'image not found'
  • Registry returns manifest not found
  • Image works locally but fails in cluster

Common causes

  1. Typo in image name or tag
  2. Image pushed to wrong registry
  3. Image deleted from registry
  4. Wrong Docker Hub repository path

How to fix "Docker image not found, manifest not found 404"

1Check image reference
bash
kubectl get pod -n <namespace> <pod-name> -o jsonpath='{.spec.containers[0].image}'
2Verify image exists
bash
docker pull <image>:<tag>
3Check registry path
bash
# Correct format:
# docker.io/library/nginx:latest  (Docker Hub official)
# docker.io/username/image:tag     (Docker Hub user)
# registry.example.com/image:tag   (Private registry)
4Update deployment with correct image
bash
kubectl set image deployment/<name> <container>=<correct-image>
5Verify pod pulls new image
bash
kubectl get pods -n <namespace> -w

Advanced notes

Use imagePullPolicy: IfNotPresent to avoid re-pulling if already cached.

Frequently asked questions

What does "IMAGE_NOT_FOUND" mean?
When Kubernetes tries to pull a container image, the registry returns 404 (not found). This means the image name, tag, or registry path is incorrect or the image was deleted.
How do I fix "IMAGE_NOT_FOUND"?
Container image specified in pod doesn't exist in registry. Fix by verifying image name, checking registry, and using correct image references.
What causes "IMAGE_NOT_FOUND"?
Typo in image name or tag Image pushed to wrong registry Image deleted from registry
Is the "IMAGE_NOT_FOUND" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading