Error map
Init:CrashLoopBackOff Pod status Init:CrashLoopBackOff / Init:Error
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)
[nodemon] app crashed - waiting for file changes before starting...
Your app threw an error on startup; nodemon is waiting for a file change to retry.
java.lang.ExceptionInInitializerError
A static initializer (static block or static field) threw an exception while the class was loading.
Job for mysql.service failed because the control process exited with error code
The MySQL/MariaDB service failed to start — the real reason is in the MySQL error log.
HTTP Error 500.30 - ASP.NET Core app failed to start
IIS/Azure’s ASP.NET Core Module launched your app but it crashed during startup.
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.
FATAL: the database system is starting up
PostgreSQL is still starting (or recovering) and not accepting connections yet.
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…
FATAL: lock file "postmaster.pid" already exists — Is another postmaster running in data directory?
PostgreSQL won’t start because a stale postmaster.pid file remains (or another instance really is running).
Pod status CreateContainerError
The image was pulled, but the container runtime failed to create the container — bad command, missing mount target, or a name/vol…
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 (30)
Error: Cannot find module 'x' (MODULE_NOT_FOUND)
Node can’t resolve the module path — the package isn’t installed, or a relative path/extension is wrong.
Error: listen EADDRINUSE: address already in use :::3000
Another process is already listening on that port.
npm ERR! could not determine executable to run
npx couldn’t find a binary to run for that package.
LOG: could not bind IPv4 address "0.0.0.0": Address already in use — Is another postmaster already running on port 5432?
Another process (often a second PostgreSQL install or a container) already listens on 5432.
Docker container exits immediately (Exited (0) / Exited (1) right after start)
The container started and its main process finished at once, so the container stopped — Docker containers only live as long as PI…
Docker container keeps restarting (Restarting (1) x seconds ago)
The container crashes on start and its restart policy (always/unless-stopped/on-failure) starts it again in a loop.
MySQL ERROR 2002 (HY000): Can't connect to local MySQL server through socket
The client couldn’t reach the MySQL server — it isn’t running, or the client is looking for the socket/port in the wrong place.
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
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.
InvalidOperationException: Unable to resolve service for type 'X' while attempting to activate 'Y'
ASP.NET Core’s dependency injection container can’t build Y because one of its constructor dependencies (X) was never registered.
Kubernetes: ImagePullBackOff / ErrImagePull
The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.
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.
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).
FATAL: data directory "/var/lib/postgresql/data" has invalid permissions — Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
PostgreSQL refuses to start because the data directory is too open or owned by the wrong user.
FATAL: database files are incompatible with server — The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16
A newer (or older) PostgreSQL major version was started on an existing data directory.
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
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.
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…
Pod stuck in Terminating state
kubectl delete pod hangs and the pod shows Terminating for minutes or forever.
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).
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 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.
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…
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