Wiki source code of Runtime Overview Exit codes
Version 8.1 by Tudor Neacsu on 2024/06/21 08:59
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 2 | 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. | ||
| 3 | |||
| 4 | Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 5 | |||
| 6 | == 1. Key concepts == | ||
| 7 | |||
| 8 | |||
| 9 | == 2. Exit code values == | ||
| 10 | |||
| 11 | * Exited with code *0*: The application inside the container completed its work successfully without any errors. | ||
| 12 | |||
| 13 | * 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. | ||
| 14 | |||
| 15 | * Exited with code 125: The docker run command was not executed successfully | ||
| 16 | |||
| 17 | * 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. | ||
| 18 | |||
| 19 | * Exited with code 127: The command was not found. This usually happens if a script is missing or the path is not set correctly. | ||
| 20 | |||
| 21 | * Exited with code 137: The container was forcefully stopped. This happens when the container exceeds its memory resource limit (OOM) | ||
| 22 | |||
| 23 | * 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. | ||
| 24 | * Exited with code 255: Container exited, returning an exit code outside the acceptable range, meaning the cause of the error is not known | ||
| 25 | |||
| 26 | |||
| 27 | == 5. Suggested Additional Readings == | ||
| 28 | For more information on resetting a H2 Database, please check out the following microlearning: | ||
| 29 | * [[Reset H2 Database>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]] | ||
| 30 | |||
| 31 | |||
| 32 | )))((({{toc/}}))){{/container}}{{/container}} |