> 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/exit-codes.md). # Exit codes How to troubleshoot exit codes Exit codes give you information about terminated containers, specifying why the container terminated. In general, a `0` exit code is successful and indicates a purposefully stopped container, while a `1` exit code indicates an error. Other exit codes (larger than 1) also indicate an error state, and contain more information about what kind of error occurred. ## Finding the exit code of a failing container You can see the latest output of your instances, including exit codes and error messages, by viewing the logs for that instance. ## Common exit codes * `137`: OOM (out of memory) indicates that your container did not have enough RAM allocated to process what it was trying to do. Sometimes this can be resolved by assigning more resources to your instances, but if it is the cause of a memory leak or similar, you might need to debug the root cause in your application. --- # 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/exit-codes.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.