Taking Docker as an example – at any given time, a Docker container can be in one of several states: To better understand the causes of container failure, let’s discuss the lifecycle of a container first. The container aborted itself using the abort() function.Ĭontainer was immediately terminated by the operating system via SIGKILL signalĬontainer attempted to access memory that was not assigned to it and was terminatedĬontainer received warning that it was about to be terminated, then terminatedĬontainer exited, returning an exit code outside the acceptable range, meaning the cause of the error is not knownīelow we’ll explain how to troubleshoot failed containers on a self-managed host and in Kubernetes, and provide more details on all of the exit codes listed above. The docker run command did not execute successfullyĪ command specified in the image specification could not be invokedįile or directory specified in the image specification was not foundĮxit was triggered with an invalid exit code (valid codes are integers between 0-255) Used by developers to indicate that the container was automatically stoppedĬontainer was stopped due to application error or incorrect reference in the image specification

Installmate check last exit code