Kubernetes pod stuck in CrashLoopBackOff, no logs

Question

kubectl logs for my pod returns nothing and the pod restarts every few seconds. How can I see why it crashes?

Tomás Ferreira · Answer

Look at the previous container and the events:
kubectl logs mypod --previous
kubectl describe pod mypod   # check Last State, Exit Code, Events
Exit code 137 is an OOM kill; 1 is usually the app itself; a missing command shows up in Events.

Oskar Lindqvist · Answer

--previous showed a missing env var. Thanks!

Kubernetes pod stuck in CrashLoopBackOff, no logs

1 Answer

Suggested topics

The Heapfield Blog

Featured on Meta