Error map
CreateContainerError Pod status CreateContainerError
Kubernetes · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (12)
OCI runtime create failed: exec: "x": executable file not found in $PATH
The command you asked the container to run doesn’t exist inside the image — wrong command name, a shell that isn’t installed (bas…
Error: INSTALLATION FAILED: cannot re-use a name that is still in use
helm install was run with a release name that already exists in the namespace (even a failed one).
error: Metrics API not available / HPA: unable to get metrics for resource cpu
metrics-server isn’t installed or isn’t working, so kubectl top and CPU/memory HorizontalPodAutoscalers have no data.
Azure Container Registry: unauthorized: authentication required, visit https://aka.ms/acr/authorization (AKS ErrImagePull 401)
Pulling/pushing to ACR wasn’t authenticated — Docker not logged in, or AKS/App Service lacks AcrPull on the registry.
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.
Job has reached the specified backoff limit (BackoffLimitExceeded)
The Job’s pods failed more times than backoffLimit (default 6), so Kubernetes marked the Job failed and stopped retrying.
Error from server: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request
A validating admission webhook (ingress-nginx, Gatekeeper/OPA, Kyverno) inspected your object and rejected it; the reason follows…
Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
Cloud Run started your container, but nothing listened on $PORT within the startup timeout — the app crashed, listens on another…
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
Kubernetes: CreateContainerConfigError — secret / configmap not found
Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t exist in that namesp…
Pod status RunContainerError
The container was created but failed to start — usually an invalid command/entrypoint, missing interpreter, or permission problem…
Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition
The kubelet couldn’t mount one of the pod’s volumes, so the pod stays in ContainerCreating.
Two steps away (32)
bash: command not found
The shell can’t find an executable with that name in any directory on your PATH.
Conflict. The container name "/x" is already in use by container …
A container (running or stopped) already has that name; Docker won’t create a second one with the same name.
exec /docker-entrypoint.sh: no such file or directory (CRLF line endings / missing interpreter)
The entrypoint file exists, but the kernel can’t run it — almost always Windows CRLF line endings in the script, or a shebang poi…
Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress
A previous Helm operation on this release was interrupted and left it in a pending-install/pending-upgrade state, so Helm refuses…
rendered manifests contain a resource that already exists. Unable to continue with install: ... invalid ownership metadata
Helm wants to create an object that already exists but isn’t labelled as belonging to this release.
Error from server (BadRequest): container "x" in pod "y" is waiting to start: ContainerCreating
kubectl logs has nothing to show yet — the container hasn’t started (still creating, pulling, or blocked).
Namespace stuck in Terminating
A deleted namespace never disappears because some resource inside it, or the namespace’s own finalizer, can’t be cleaned up.
pods is forbidden: failed quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory
A ResourceQuota on the namespace covers CPU/memory, so every pod must declare those requests/limits — and this one doesn’t.
Docker: Bind for 0.0.0.0:80 failed: port is already allocated
Another container or host process already publishes that host port.
Kubernetes: ImagePullBackOff / ErrImagePull
The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.
npm ERR! code EROFS — EROFS: read-only file system
npm tried to write to a read-only location (read-only container filesystem, mounted volume, or system path).
docker: invalid reference format (repository name must be lowercase)
Docker couldn’t parse the image name — uppercase letters, spaces, an empty variable, or a misplaced option.
Pod status Init:CrashLoopBackOff / Init:Error
An init container keeps failing, so the pod’s main containers never start.
Azure VM: OSProvisioningTimedOut — OS Provisioning for VM did not finish in the allotted time
The VM booted but its guest agent didn’t report provisioning success in time — usually a generalisation problem with a custom ima…
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
The Deployment is invalid: spec.selector: Invalid value: field is immutable
You tried to change a field Kubernetes doesn’t allow to change after creation — Deployment selectors, Job templates, Service clus…
Readiness probe failed: HTTP probe failed with statuscode: 503 / connect: connection refused
The container is running, but its readiness check fails, so the pod is marked not ready and removed from Service endpoints.
Liveness probe failed ... Container will be restarted (also Startup probe failed)
The kubelet’s liveness (or startup) check failed enough times that it killed and restarted the container.
Kubernetes node NotReady (Kubelet stopped posting node status)
The control plane hasn’t heard from a node’s kubelet, or the kubelet reports a problem — pods there stop being scheduled and are…
exec /usr/local/bin/docker-entrypoint.sh: exec format error
The container tried to run a binary built for a different CPU architecture (arm64 vs amd64) — or a script with a broken shebang /…
ECS task stopped: CannotPullContainerError: pull image manifest has been retried ... / ref pull has been retried
The ECS task couldn’t pull its image — no network route to the registry, missing ECR permissions, or a wrong image tag.
ECS: Essential container in task exited (task keeps stopping)
The main (essential) container stopped, so ECS stopped the whole task and the service keeps replacing it.
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
Azure App Service: ":( Application Error" / container didn’t respond to HTTP pings
App Service started your app but it crashed or never listened on the expected port.
Segmentation fault (core dumped)
A program accessed memory it wasn’t allowed to, and the kernel killed it with SIGSEGV (exit code 139).
KeyError: 'x'
You accessed a dictionary key that doesn’t exist.
Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available
The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume constraints.
hint: You have divergent branches and need to specify how to reconcile them.
Git 2.27+ asks you to choose merge, rebase or fast-forward-only when local and remote both have new commits.
exec /entrypoint.sh: permission denied (container won't start)
The entrypoint or command isn’t marked executable inside the image, or it’s on a volume mounted noexec.
Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
You’re accessing blob/queue data with Microsoft Entra ID, but the identity has only management roles (Owner/Contributor) — not a…
QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value exceeded the quota
localStorage/sessionStorage is full (about 5 MB per origin) or storage is disabled.
MySQL ERROR 126 (HY000): Incorrect key file for table; try to repair it
MySQL can’t use a table’s index file — usually a full tmp disk during a query, or MyISAM corruption.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException