GitList

Browse code

Add some details about the lifecycle of commands started with docker exec

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>

Sven Dowideit authored on 2014/11/11 14:54:31
Showing 2 changed files

docs/man/docker-exec.1.md index d5ec126..38ba3de 100644
docs/sources/reference/commandline/cli.md index 50c0ff3..e0a7b23 100644

docs/man/docker-exec.1.md

History View file @ 4473874

@@ -15,6 +15,12 @@ docker-exec - Run a command in a running container
                      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*

docs/sources/reference/commandline/cli.md

History View file @ 4473874

@@ -646,7 +646,11 @@ You'll need two shells for this example.
                      The `docker exec` command runs a new command in a running container.
                     -The `docker exec` command will typically be used after `docker run` or `docker start`.
                     +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.
                      #### Examples