Skip to content

Commit

Permalink
Add exit status to docker exec manpage
Browse files Browse the repository at this point in the history
There's little way of knowing what each exit status means at present
because it's not documented. I'm assuming they are the same as docker
run.

Signed-off-by: Eric Curtin <[email protected]>
  • Loading branch information
ericcurtin authored and Eric Curtin committed Feb 25, 2019
1 parent db166da commit 2367096
Showing 1 changed file with 26 additions and 0 deletions.
26 changes: 26 additions & 0 deletions man/src/container/exec.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,3 +23,29 @@ the same capabilities as the container, which may be limited. Set
--user [user | user:group | uid | uid:gid | user:gid | uid:group ]

Without this argument the command will be run as root in the container.

# Exit Status

The exit code from `docker exec` gives information about why the container
failed to exec or why it exited. When `docker exec` exits with a non-zero code,
the exit codes follow the `chroot` standard, see below:

**_126_** if the **_contained command_** cannot be invoked

$ docker exec busybox /etc; echo $?
# exec: "/etc": permission denied
docker: Error response from daemon: Contained command could not be invoked
126

**_127_** if the **_contained command_** cannot be found

$ docker exec busybox foo; echo $?
# exec: "foo": executable file not found in $PATH
docker: Error response from daemon: Contained command not found or does not exist
127

**_Exit code_** of **_contained command_** otherwise

$ docker exec busybox /bin/sh -c 'exit 3'
# 3

0 comments on commit 2367096

Please sign in to comment.