From e29f6719f71baf0a1bda8d485ae150fa51f23bb4 Mon Sep 17 00:00:00 2001 From: Eric Hawicz Date: Fri, 26 Nov 2021 08:04:14 -0500 Subject: [PATCH] Note the max-retries option on the Start containers automatically page. (#13787) * Note the max-retries option on the Start containers automatically page. * Update format Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com> --- config/containers/start-containers-automatically.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/containers/start-containers-automatically.md b/config/containers/start-containers-automatically.md index b73c66c7c8..7deddd6590 100644 --- a/config/containers/start-containers-automatically.md +++ b/config/containers/start-containers-automatically.md @@ -27,7 +27,7 @@ any of the following: | Flag | Description | |:-----------------|:------------------------------------------------------------------------------------------------| | `no` | Do not automatically restart the container. (the default) | -| `on-failure` | Restart the container if it exits due to an error, which manifests as a non-zero exit code. | +| `on-failure`(optional:`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 retries the Docker daemon attempts. | | `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. |