Difference between revisions of "Docker start configuration behavior and restart policy"

From wikieduonline
Jump to navigation Jump to search
Line 24: Line 24:
 
* <code>[[docker-compose.yml]]</code>
 
* <code>[[docker-compose.yml]]</code>
 
* [[HEALTHCHECK]]
 
* [[HEALTHCHECK]]
 +
* [[systemd]] and <code>[[service]]</code>
  
 
== See also ==
 
== See also ==

Revision as of 11:37, 13 February 2020

To configure the start configuration behavior or the restart policy for a container (both of them), use the --restart flag when using the docker run command. The value of the --restart flag can be any of the following:

  • Do not automatically restart the container. (the default): no
  • Restart the container if it exits due to an error, which manifests as a non-zero exit code: on-failure
  • Restart the container unless it is explicitly stopped or Docker itself is stopped or restarted: unless-stopped
  • Always restart the container if it stops: always


The following example starts a Redis container and configures it to always restart unless it is explicitly stopped or Docker is restarted:

$ docker run -dit --restart unless-stopped redis With docker inspect CONTAINER[1] you can verify RestartPolicy configuration.

To update restart policy execute:

docker update[2] --restart=always CONTAINER_ID|CONTAINER_NAME[3]
If the container is started with “--rm” flag, you cannot update the restart policy for it. The AutoRemove and RestartPolicy are mutually exclusive for the container.
 docker inspect -f "{{ .HostConfig.RestartPolicy }}"  CONTAINER_NAME

Related commands

See also

  • https://stackoverflow.com/questions/43108227/is-it-possible-to-show-the-restart-policy-of-a-running-docker-container
  • https://docs.docker.com/engine/reference/commandline/update/
  • docker update --restart=always 90bf248337dc
  • Advertising: