mirror of https://github.com/docker/docs.git
Merge pull request #18228 from dvdksn/engine-on-failure-daemon-restart
clarify restart-policy on-failure with daemon restart
This commit is contained in:
David Karlsson
GitHub
commit
6c31b96697
|
|
@ -10,13 +10,13 @@ aliases:
|
|||
|
||||
Docker provides [restart policies](../../engine/reference/run.md#restart-policies---restart)
|
||||
to control whether your containers start automatically when they exit, or when
|
||||
Docker restarts. Restart policies ensure that linked containers are started in
|
||||
the correct order. Docker recommends that you use restart policies, and avoid
|
||||
using process managers to start containers.
|
||||
Docker restarts. Restart policies start linked containers in the correct order.
|
||||
Docker recommends that you use restart policies, and avoid using process
|
||||
managers to start containers.
|
||||
|
||||
Restart policies are different from the `--live-restore` flag of the `dockerd`
|
||||
command. Using `--live-restore` allows you to keep your containers running
|
||||
during a Docker upgrade, though networking and user input are interrupted.
|
||||
command. Using `--live-restore` lets you to keep your containers running during
|
||||
a Docker upgrade, though networking and user input are interrupted.
|
||||
|
||||
## Use a restart policy
|
||||
|
||||
|
|
@ -25,26 +25,27 @@ when using the `docker run` command. The value of the `--restart` flag can be
|
|||
any of the following:
|
||||
|
||||
| Flag | Description |
|
||||
|:-----------------|:------------------------------------------------------------------------------------------------|
|
||||
| `no` | Do not automatically restart the container. (the default) |
|
||||
| `on-failure[:max-retries]` | Restart the container if it exits due to an error, which manifests as a non-zero exit code. Optionally, limit the number of times the Docker daemon attempts to restart the container using the `:max-retries` option. |
|
||||
| `always` | Always restart the container if it stops. If it is manually stopped, it is restarted only when Docker daemon restarts or the container itself is manually restarted. (See the second bullet listed in [restart policy details](#restart-policy-details)) |
|
||||
| `unless-stopped` | Similar to `always`, except that when the container is stopped (manually or otherwise), it is not restarted even after Docker daemon restarts. |
|
||||
| :------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `no` | Don't automatically restart the container. (Default) |
|
||||
| `on-failure[:max-retries]` | Restart the container if it exits due to an error, which manifests as a non-zero exit code. Optionally, limit the number of times the Docker daemon attempts to restart the container using the `:max-retries` option. The `on-failure` policy only prompts a restart if the container exits with a failure. It doesn't restart the container if the daemon restarts. |
|
||||
| `always` | Always restart the container if it stops. If it's manually stopped, it's restarted only when Docker daemon restarts or the container itself is manually restarted. (See the second bullet listed in [restart policy details](#restart-policy-details)) |
|
||||
| `unless-stopped` | Similar to `always`, except that when the container is stopped (manually or otherwise), it isn't restarted even after Docker daemon restarts. |
|
||||
|
||||
The following example starts a Redis container and configures it to always
|
||||
restart unless it is explicitly stopped or Docker is restarted.
|
||||
The following command starts a Redis container and configures it to always
|
||||
restart, unless the container is explicitly stopped, or the daemon restarts.
|
||||
|
||||
```console
|
||||
$ docker run -d --restart unless-stopped redis
|
||||
```
|
||||
|
||||
This command changes the restart policy for an already running container named `redis`.
|
||||
The following command changes the restart policy for an already running
|
||||
container named `redis`.
|
||||
|
||||
```console
|
||||
$ docker update --restart unless-stopped redis
|
||||
```
|
||||
|
||||
And this command will ensure all currently running containers will be restarted unless stopped.
|
||||
The following command ensures all running containers restart.
|
||||
|
||||
```console
|
||||
$ docker update --restart unless-stopped $(docker ps -q)
|
||||
|
|
@ -57,17 +58,16 @@ Keep the following in mind when using restart policies:
|
|||
- A restart policy only takes effect after a container starts successfully. In
|
||||
this case, starting successfully means that the container is up for at least
|
||||
10 seconds and Docker has started monitoring it. This prevents a container
|
||||
which does not start at all from going into a restart loop.
|
||||
which doesn't start at all from going into a restart loop.
|
||||
|
||||
- If you manually stop a container, its restart policy is ignored until the
|
||||
Docker daemon restarts or the container is manually restarted. This is another
|
||||
attempt to prevent a restart loop.
|
||||
- If you manually stop a container, the restart policy is ignored until the
|
||||
Docker daemon restarts or the container is manually restarted. This prevents
|
||||
a restart loop.
|
||||
|
||||
- Restart policies only apply to _containers_. Restart policies for swarm
|
||||
services are configured differently. See the
|
||||
- Restart policies only apply to containers. To configure restart policies for
|
||||
Swarm services, see
|
||||
[flags related to service restart](../../engine/reference/commandline/service_create.md).
|
||||
|
||||
|
||||
## Use a process manager
|
||||
|
||||
If restart policies don't suit your needs, such as when processes outside
|
||||
|
|
@ -78,8 +78,8 @@ Docker depend on Docker containers, you can use a process manager such as
|
|||
|
||||
> **Warning**
|
||||
>
|
||||
> Do not try to combine Docker restart policies with host-level process managers,
|
||||
> because this creates conflicts.
|
||||
> Don't combine Docker restart policies with host-level process managers,
|
||||
> as this creates conflicts.
|
||||
{ .warning }
|
||||
|
||||
To use a process manager, configure it to start your container or service using
|
||||
|
|
@ -94,8 +94,8 @@ running and starts/restart it if not.
|
|||
|
||||
> **Warning**
|
||||
>
|
||||
> These are not Docker-aware and just monitor operating system processes within
|
||||
> the container. Docker does not recommend this approach, because it is
|
||||
> platform-dependent and even differs within different versions of a given Linux
|
||||
> These aren't Docker-aware, and only monitor operating system processes within
|
||||
> the container. Docker doesn't recommend this approach, because it's
|
||||
> platform-dependent and may differ between versions of a given Linux
|
||||
> distribution.
|
||||
{ .warning }
|
||||
Loading…
Reference in New Issue