mirror of
https://github.com/containers/buildah.git
synced 2026-02-05 18:44:58 +01:00
2f671a26b2
Buildah run was exiting with the correct exit code, when a container failed. Buildah bud was not, so this should fix this. Also switched to the proper exit codes when containers fail. When Buildah fails to execute it will exit with a 125 exit code like Podman does. If a command fails to execute inside of a container we will exit with a 126. Currently we do not support the 127 for exiting when the command does not exist. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
14 lines
527 B
Go
14 lines
527 B
Go
package cli
|
|
|
|
const (
|
|
// ExecErrorCodeGeneric is the default error code to return from an exec session if libpod failed
|
|
// prior to calling the runtime
|
|
ExecErrorCodeGeneric = 125
|
|
// ExecErrorCodeCannotInvoke is the error code to return when the runtime fails to invoke a command
|
|
// an example of this can be found by trying to execute a directory:
|
|
// `podman exec -l /etc`
|
|
ExecErrorCodeCannotInvoke = 126
|
|
// ExecErrorCodeNotFound is the error code to return when a command cannot be found
|
|
ExecErrorCodeNotFound = 127
|
|
)
|