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

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

KubernetesBEGINNERMEDIUM

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

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

Typo in image name or tag
Image pushed to wrong registry
Image deleted from registry
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>

Advanced notes

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

Related errors

Official resources & further reading

📚Kubernetes Official Documentation
📖
Images - Kubernetes Docs(Official Docs)