Runtime Overview Exit codes

In this microlearning, we will give insights into what is an exit code, the main exit codes returned by a container when it stops and how can that help a Support Engineer to conduct an RCA.  

Should you have any questions, please get in touch with academy@emagiz.com.

1. Key concepts

2. Exit code values

• Exited with code *0*: The application inside the container completed its work successfully without any errors.

• Exited with code 1: There was a general error in the application, which could be due to a variety of reasons like incorrect arguments or a failed dependency.

• Exited with code 125: The docker run command was not executed successfully 

• Exited with code 126: The command inside the container was found but cannot be executed. This can be due to permission issues or if the command is not executable.

• Exited with code 127: The command was not found. This usually happens if a script is missing or the path is not set correctly.

• Exited with code 137: The container was forcefully stopped. This happens when the container exceeds its memory resource limit (OOM)

• Exited with code 139: The application inside the container crashed due to a segmentation fault, which is usually caused by accessing memory that the process does not have permission to access.
• Exited with code 255: Container exited, returning an exit code outside the acceptable range, meaning the cause of the error is not known

5. Suggested Additional Readings

For more information on resetting a H2 Database, please check out the following microlearning:

• Reset H2 Database