# kubernetes

Exit code 137 means the process received SIGKILL (128 + 9). In Kubernetes it almost always means the container breached its own memory limit and the cgroup OOM killer ended it — a different failure from the node running out of memory, which evicts the pod instead.

/k/container-exit-code-137-oomkilled · kubernetes · 4 sources · verified 2026-08-07 · 137 OOMKilled SIGKILL

The image pulled fine, but the kubelet cannot assemble the container's configuration: a referenced ConfigMap or Secret does not exist, or exists without the key the pod asks for. The pod stays in Waiting and no container is ever created.

/k/kubernetes-createcontainerconfigerror · kubernetes · 3 sources · verified 2026-08-07 · CreateContainerConfigError

CrashLoopBackOff is not an error in itself — it is the kubelet waiting between restarts of a container that keeps exiting. The exit code and reason on the previous container instance identify the actual failure; the backoff only controls how long you wait to see it again.

/k/kubernetes-crashloopbackoff · kubernetes · 4 sources · verified 2026-08-07 · CrashLoopBackOff BackOff

The kubelet cannot pull the image, so the container never starts. ErrImagePull is the first failure and ImagePullBackOff is the wait between retries — neither says why. The registry's own error text, printed in the pod's Events, is what identifies the cause.

/k/kubernetes-imagepullbackoff · kubernetes · 4 sources · verified 2026-08-07 · ImagePullBackOff ErrImagePull