a2b529ead2
--help and help are successful commands so output should not go to error.
QE teams have requested this change, also users doing docker help | less
or docker run --help | less would expect this to work.
Usage statement should only be printed when the user asks for it.
Errors should print error message and then suggest the docker COMMAND --help
command to see usage information.
The current behaviour causes the user to have to search for the error message
and sometimes scrolls right off the screen. For example a error on a
"docker run" command is very difficult to diagnose.
Finally erros should always exit with a non 0 exit code, if the user
makes a CLI error.
Docker-DCO-1.1-Signed-off-by: Dan Walsh <dwalsh@redhat.com> (github: rhatdan)
1.1 KiB
% DOCKER(1) Docker User Manuals % Docker Community % JUNE 2014
NAME
docker-exec - Run a command in a running container
SYNOPSIS
docker exec [-d|--detach[=false]] [--help] [-i|--interactive[=false]] [-t|--tty[=false]] CONTAINER COMMAND [ARG...]
DESCRIPTION
Run a process in a running container.
The command started using docker exec will only run while the container's primary
process (PID 1) is running, and will not be restarted if the container is restarted.
If the container is paused, then the docker exec command will wait until the
container is unpaused, and then run
OPTIONS
-d, --detach=true|false Detached mode: run command in the background. The default is false.
--help Print usage statement
-i, --interactive=true|false Keep STDIN open even if not attached. The default is false.
-t, --tty=true|false Allocate a pseudo-TTY. The default is false.
The -t option is incompatible with a redirection of the docker client standard input.
HISTORY
November 2014, updated by Sven Dowideit SvenDowideit@home.org.au