Skip to Content
Last modified by Carlijn Kokkeler on 2024/09/17 15:13
From version 15.1
edited by Erik Bakker
on 2024/06/21 14:52
Change comment: There is no comment for this version
To version 17.1
edited by Tudor Neacsu
on 2024/06/21 15:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.TudorNeacsu
Content
... ... @@ -5,7 +5,7 @@
5 5  
6 6  == 1. Key concepts ==
7 7  
8 -In a previous [[microlearning>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Microlearnings/Crash%20Course/Crash%20Course%20Platform/Runtime%20Overview||target="blank"]] [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.Runtime Overview||target="blank"]] we explained that a container can have multiple statuses. Among these, there is the status Exit which is returned by the container uppon stopping and comes together with a code. The exit code usually points out the reason why the container stopped. In the section below we go into more details for the most common exit codes that you could see in eMagiz.
8 +In a previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.Runtime Overview||target="blank"]] we explained that a container can have multiple statuses. Among these, there is the status Exit which is returned by the container uppon stopping and comes together with a code. The exit code usually points out the reason why the container stopped. In the section below we describe the most common exit codes that you can encounter in eMagiz.
9 9  
10 10  [[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-runtime-overview-exit-codes.png]]
11 11  
... ... @@ -37,7 +37,7 @@
37 37  ** 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.
38 38  
39 39  * Exited with code **143**
40 -** The container stopped gracefully terminated after receiving the operating system's SIGTERM signal, which instructs the container to do so.
40 +** The container stopped gracefully after receiving the operating system's SIGTERM signal, which instructs the container to do so.
41 41  ** For example, when you command the container to stop via Deploy Architecture or when eMagiz stops the container, e.g. Stop Machine deployment step.
42 42  
43 43  * Exited with code **255**
... ... @@ -44,7 +44,6 @@
44 44  ** Container exited, returning an exit code outside the acceptable range, meaning the cause of the error is not known.
45 45  
46 46  
47 -== 5. Suggested Additional Readings ==
48 48  
49 49  
50 50  )))((({{toc/}}))){{/container}}{{/container}}