InvalidImageName Kubernetes Origin: Platform & cloud Last updated 12 Oct 2026

Pod status InvalidImageName: couldn't parse image reference

The image field in the pod spec isn’t a valid image reference, so the kubelet can’t even try to pull it.

Exact message you may see couldn't parse image referenceFailed to apply default image taginvalid reference format
Seen on: Kubernetes

Meaning

Kubernetes rejects references with uppercase letters, spaces, a trailing colon (image: app:), double slashes or unrendered template placeholders (image: {{ .Values.image }}). Helm/Kustomize values that came out empty are the most common cause.

Common causes

  • Empty tag variable producing app: or app:@
  • Uppercase letters or spaces in the name
  • Unrendered template/placeholder in the manifest
  • Protocol prefix (https://) in the image name

⚡ Quick fix

  1. kubectl describe pod to see the exact reference
  2. Fix the image value in values.yaml/kustomization
  3. Render locally and inspect: helm template / kustomize build

Detailed fix by platform

Kubernetes

  1. bash
    kubectl get pod web-0 -o jsonpath='{.spec.containers[*].image}'
    helm template ./chart | grep -n 'image:'

How to diagnose

  1. Reference — Exact image string in the pod spec
  2. Templates — Rendered values empty?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

1011 — Cloudflare Error 1011: Access denied (Hotlinking denied) (Cloudflare)1011CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOffCreateContainerError — Pod status CreateContainerError (Kubernetes)CreateContainerErrorFailedMount — Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition (Kubernetes)FailedMountImagePullBackOff — Kubernetes: ImagePullBackOff / ErrImagePull (Kubernetes)ImagePullBackOffInit:CrashLoopBackOff — Pod status Init:CrashLoopBackOff / Init:Error (Kubernetes)Init:CrashLoopBackOffinvalid reference format — docker: invalid reference format (repository name must be lowercase) (Docker)invalid reference for…is waiting to start — Error from server (BadRequest): container "x" in pod "y" is waiting to start: ContainerCreating (Kubernetes)is waiting to startInvalidIm…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.