Skip to content

Image Not Found

Error message

                Error: image devops/app:v2 not found
              

Quick summary

Kubernetes or Docker cannot find the specified image, usually because it does not exist, is in the wrong registry, or authentication is missing.

Why this happens

  • The image name or tag is misspelled

  • The image has not been built and pushed to the registry

  • The registry URL is incorrect or the image is in a different registry

  • Missing registry credentials — the cluster cannot authenticate to pull the image

Minimal example

✗ Broken code
spec:
  containers:
    - name: app
      image: myapp:v2  # image v2 was never pushed
✓ Fixed code
spec:
  containers:
    - name: app
      image: myapp:v1  # use the existing version

The broken code references an image version that was never pushed. The fix uses a version that exists in the registry.

How to diagnose

  • Verify the image name and tag with docker images or check the registry

  • Check if the image exists in the registry: docker pull <image>

  • Verify the imagePullPolicy and image reference in your Kubernetes manifest

  • Check for ImagePullSecrets if using a private registry

How to fix

  • Correct the image name and tag in your deployment manifest

  • Build and push the image: docker build -t <image> . && docker push <image>

  • Create an imagePullSecret for private registries and reference it in the Pod spec

  • Ensure the registry URL is correct (e.g., registry.example.com/myapp:v1)

How to prevent

  • Use a CI pipeline to automatically build and push images on every commit

  • Use explicit version tags instead of latest to avoid ambiguity

  • Set up imagePullSecrets for private registries in your namespace

Related Resources

Related Glossary

← Back to language