Pod Keeps Restarting (CrashLoopBackOff)

If a pod is starting, failing and restarting over and over, this article explains the usual causes and how to fix them.

A pod in CrashLoopBackOff is starting, failing, and being restarted over and
over. The usual causes, most likely first:

• The application fails to start — a missing environment variable or bad
  configuration.
• The liveness probe is failing before the application has finished starting up.
  Adding or lengthening a startup probe is the fix.
• The pod is exceeding its memory limit (see the next section).

Check the Logs tab first. If you have namespace access and need more detail:

# Logs from the container that crashed
kubectl logs <pod-name> -n <your-namespace> --previous

# Events showing the exit reason
kubectl describe pod <pod-name> -n <your-namespace>

Fix the cause in your Component's configuration and click Save.

Still having issues?

Raise a request with the namespace, the Component name, the pod status, and what
you have already tried.

Related articles

• Workload Management — resource requests, limits and health checks
• Troubleshooting Common Issues — find your symptom