Provided by: docker.io_17.12.1-0ubuntu1_amd64 bug


       docker-container-exec - Run a command in a running container


       docker container exec [OPTIONS] CONTAINER COMMAND [ARG...]


       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


       privileged gives the process extended Linux capabilities ⟨
       pages/man7/capabilities.7.html⟩ when running in a container.

       Without this flag, the process run by docker exec in a running container has the same
       capabilities as the container, which may be limited. Set --privileged to give all
       capabilities to the process.


       user sets the username or UID used and optionally the groupname or GID for the specified

       The followings examples are all valid:
          --user [user | user:group | uid | uid:gid | user:gid | uid:group ]

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


       -d, --detach[=false]
           Detached mode: run command in the background

           Override the key sequence for detaching a container

       -e, --env=
           Set environment variables

       -h, --help[=false]
           help for exec

       -i, --interactive[=false]
           Keep STDIN open even if not attached

           Give extended privileges to the command

       -t, --tty[=false]
           Allocate a pseudo-TTY

       -u, --user=""
           Username or UID (format: <name|uid>[:<group|gid>])

       -w, --workdir=""
           Working directory inside the container