Pod in CrashLoopBackOff in Kubernetes - Commands & Configuration

Introduction

Sometimes, a Kubernetes pod keeps restarting because its application crashes repeatedly. This state is called CrashLoopBackOff. It means Kubernetes tries to start the pod, but the app inside fails quickly and Kubernetes waits before trying again.

When your application inside a pod crashes immediately after starting.

When you want to check why a pod is not staying up and running.

When you need to debug startup errors in your containerized app.

When Kubernetes shows a pod status as CrashLoopBackOff in your cluster.

When you want to fix configuration or code issues causing pod crashes.

Commands

This command lists all pods in the current namespace and shows their status, including if any pod is in CrashLoopBackOff.

Terminal

kubectl get pods

Expected Output

NAME           READY   STATUS             RESTARTS   AGE

example-pod    0/1     CrashLoopBackOff   3          2m

This command shows detailed information about the pod, including events and error messages explaining why the pod is crashing.

Terminal

kubectl describe pod example-pod

Expected Output

Name:           example-pod

Namespace:      default

Status:         Running

Containers:

  example-container:

    State:          Waiting

    Reason:         CrashLoopBackOff

    Last State:     Terminated

      Exit Code:   1

      Started:     Thu, 01 Jun 2023 10:00:00 +0000

      Finished:    Thu, 01 Jun 2023 10:00:10 +0000

Events:

  Type     Reason     Age                    From               Message

  ----     ------     ----                   ----               -------

  Warning  BackOff    2m (x3 over 2m)        kubelet            Back-off restarting failed container

This command fetches the logs from the crashing container to see error messages or clues about why it fails.

Terminal

kubectl logs example-pod

Expected Output

Error: failed to start application: missing configuration file

Usage: example-app [options]

This command deletes the crashing pod so Kubernetes can create a fresh pod, useful after fixing the problem.

Terminal

kubectl delete pod example-pod

Expected Output

pod "example-pod" deleted

Key Concept

If you remember nothing else from this pattern, remember: CrashLoopBackOff means your pod's app crashes repeatedly and you must check logs and events to find the cause.

Common Mistakes

Ignoring pod logs and only looking at pod status

Pod status CrashLoopBackOff only tells the pod is crashing, not why. Without logs, you cannot fix the root cause.

Always check pod logs with 'kubectl logs' to see error messages causing the crash.

Deleting the pod repeatedly without fixing the error

Deleting the pod restarts it but does not fix the underlying problem, so it will crash again.

Investigate logs and events first, fix the app or config, then delete the pod to restart cleanly.

Summary

Use 'kubectl get pods' to identify pods in CrashLoopBackOff state.

Use 'kubectl describe pod' to see detailed pod events and error reasons.

Use 'kubectl logs' to read the container's error messages causing the crash.

Fix the root cause, then delete the pod to let Kubernetes recreate it.