> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/guides-and-examples/running-instances/troubleshooting/crash-loop-backoff.md). # CrashLoopBackoff error 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. #### Troubleshooting a CrashLoopBackOff error 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 `sleep` step. This will force the container to stay alive and give you time to figure out the problem. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.release.com/guides-and-examples/running-instances/troubleshooting/crash-loop-backoff.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.