Comment on page
How to troubleshoot a CrashLoopBackOff error
A CrashLoopBackOff error in Kubernetes means that an instance is constantly crashing. After each crash, the instance restarts, but this does not fix the problem, and it crashes again, leading to a loop.
The underlying cause of a CrashLoopBackOff error is usually somewhere in your application, so it can be hard to track down.
Take the following steps:
- Click on the instance in the Release UI and look at the crash reason.
- Look at the exit codes, which might describe what caused the crash.
- Look at the logs before the crash to see if anything else went wrong.
If the container dies too quickly and you can't debug effectively, you can modify the run command for that instance and add a
sleepstep. This will force the container to stay alive and give you time to figure out the problem.