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

Pod status RunContainerError

The container was created but failed to start — usually an invalid command/entrypoint, missing interpreter, or permission problem at exec time.

Exact message you may see failed to start containerOCI runtime start failedfailed to create shim task
Seen on: Kubernetes

Meaning

RunContainerError means the runtime’s start call failed, often with “exec: … executable file not found in $PATH”, “permission denied” or a cgroup/seccomp error. It may cycle into CrashLoopBackOff.

Common causes

  • Entrypoint/command not found or not executable
  • Script with CRLF line endings
  • securityContext (readOnlyRootFilesystem, runAsUser) blocks start
  • Node runtime/cgroup problem

⚡ Quick fix

  1. kubectl describe pod for the start error
  2. Test the image locally with docker run
  3. Fix command, permissions or securityContext

Detailed fix by platform

Kubernetes

  1. bash
    kubectl describe pod web-0 | grep -A5 'Last State'
    kubectl run debug --rm -it --image=myimage:1.0 --command -- sh

How to diagnose

  1. Message — Start error in events
  2. Image — Works with docker run?
  3. Security — runAsUser/readOnly settings

🔧 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 unauthorizedContainer 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)CrashLoopBackOffCreateContainerError — Pod status CreateContainerError (Kubernetes)CreateContainerErrorexec permission denied — exec /entrypoint.sh: permission denied (container won't start) (Docker)exec permission deniedFailedMount — Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition (Kubernetes)FailedMountInit:CrashLoopBackOff — Pod status Init:CrashLoopBackOff / Init:Error (Kubernetes)Init:CrashLoopBackOffInvalidImageName — Pod status InvalidImageName: couldn't parse image reference (Kubernetes)InvalidImageNameRunContai…

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.