It is a good idea to start your troubleshooting by recreating the container. The result will look something like this: Containers:ĭIY Troubleshooting Techniques 1. If you are running containers as part of a Kubernetes cluster, you can find the exit code by gathering information about a pod. If there are no invalid references, check the logs for a clue that might indicate which library within the container caused the error, and debug the library.If so, the container probably exited because of this invalid reference. Check if a file listed in the image specification was not found.
To diagnose why your container exited, look at the container engine logs: To list all containers that exited with an error code or didn’t start correctly: The number in the brackets is the Exit Code. When a container exits, the container engine’s command-line interface (CLI) displays a line like this. To send Signal 7 (SIGHUP) to a Linux process use the following command: kill - HUB In old terminals based on the RS-232 protocol, SIGHUP was a “hang up” indicating the terminal has shut down. Signal 7 is also known as SIGHUP – a term that originates from POSIX-compliant terminals. When a container terminates with Exit Code 1, the operating system terminates the container’s process with Signal 7. In Unix or Linux operating systems, signals help manage the process lifecycle.
For example, if a Java library is running within the container, and the library throws a compiler error, the container might terminate with Exit Code 1.Īn invalid reference is a file reference in the image used to run the container, which points to a nonexistent file. Exit Code 1 means that a container terminated, typically due to an application error or an invalid reference.Īn application error is a programming error in any code running within the container.
0 kommentar(er)
