1berry/docker-cli
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Document that there is a delay before the --restart policy restart, and that its double the last one

Browse Source 
Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@docker.com> (github: SvenDowideit)

Signed-off-by: Sven Dowideit <SvenDowideit@docker.com>
This commit is contained in:
Sven Dowideit 2014-12-30 12:14:08 +10:00 committed by Tibor Vass
parent 04e44cef6b
commit 6345932ff1
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/sources/reference/commandline/cli.md
View File

@ -1768,6 +1768,16 @@ application change:
Using the `--restart` flag on Docker run you can specify a restart policy for
how a container should or should not be restarted on exit.
An ever increasing delay (double the previous delay, starting at 100 milliseconds)
is added before each restart to prevent flooding the server. This means the daemaon
will wait for 100 mS, then 200 mS, 400, 800, 1600, and so on until either the
`on-failure` limit is hit, or when you `docker stop` or even `docker rm -f`
the container.
When a restart policy is active on a container, it will be shown in `docker ps`
as either `Up` or `Restarting` in `docker ps`. It can also be useful to use
`docker events` to see the restart policy in effect.
** no ** - Do not restart the container when it exits.
** on-failure ** - Restart the container only if it exits with a non zero exit status.