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