Pod status RunContainerError
The container was created but failed to start — usually an invalid command/entrypoint, missing interpreter, or permission problem at exec time.
failed to start containerOCI runtime start failedfailed to create shim task 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
- kubectl describe pod for the start error
- Test the image locally with docker run
- Fix command, permissions or securityContext
Detailed fix by platform
Kubernetes
- bash
kubectl describe pod web-0 | grep -A5 'Last State' kubectl run debug --rm -it --image=myimage:1.0 --command -- sh
How to diagnose
- Message — Start error in events
- Image — Works with docker run?
- 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:
Similar errors
- ACR unauthorized Azure Container Registry: unauthorized: authentication required, visit https://aka.ms/acr/authorization (AKS ErrImagePull 401)
- 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
- CrashLoopBackOff Kubernetes: CrashLoopBackOff
Most viewed in Kubernetes
- provided port is not in the valid range spec.ports[0].nodePort: Invalid value: 80: provided port is not in the valid range. The range of valid ports is 30000-32767
- the object has been modified Operation cannot be fulfilled on deployments.apps "x": the object has been modified; please apply your changes to the latest version and try again
- error converting YAML to JSON error converting YAML to JSON: yaml: line 12: did not find expected key
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 13 Oct 2026