CreateContainerError Kubernetes Origin: Platform & cloud OSI layer 7 · Application Last updated 13 Oct 2026

Pod status CreateContainerError

The image was pulled, but the container runtime failed to create the container — bad command, missing mount target, or a name/volume conflict.

Exact message you may see Error: failed to create containerd containerfailed to generate container spec
Seen on: Kubernetes

Meaning

Unlike CreateContainerConfigError (missing Secret/ConfigMap), this comes from the runtime itself. The Events section of kubectl describe pod has the real message: executable not found, subPath errors, “container name already in use”, or a read-only filesystem problem.

Common causes

  • command/args reference an executable not in the image
  • subPath or volume mount target invalid
  • Leftover container with the same name on the node
  • Runtime/storage problem on the node

⚡ Quick fix

  1. Read the event message with kubectl describe pod
  2. Fix command/args or mounts
  3. Delete the pod so it’s recreated (or cordon a bad node)

Detailed fix by platform

Kubernetes

  1. kubectl describe pod web-7d9c -n app | sed -n '/Events/,$p'

How to diagnose

  1. Events — Exact runtime message
  2. Command — Does the binary exist in the image?
  3. Node — Only on one node?

🔧 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):

ACR unauthorized — Azure Container Registry: unauthorized: authentication required, visit https://aka.ms/acr/authorization (AKS ErrImagePull 401) (Azure)ACR unauthorizedadmission webhook denied the request — Error from server: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request (Kubernetes)admission webhook den…BackoffLimitExceeded — Job has reached the specified backoff limit (BackoffLimitExceeded) (Kubernetes)BackoffLimitExceededcannot re-use a name that is still in use — Error: INSTALLATION FAILED: cannot re-use a name that is still in use (Kubernetes)cannot re-use a name …Container failed to start — Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable (Google Cloud / Firebase)Container failed to s…CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOffCreateContainerConfigError — Kubernetes: CreateContainerConfigError — secret / configmap not found (Kubernetes)CreateContainerConfig…executable file not found in $PATH — OCI runtime create failed: exec: "x": executable file not found in $PATH (Docker)executable file not f…CreateCon…

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.