From 42b9fec12a4d3840f32c2a810077a06e8101a6dc Mon Sep 17 00:00:00 2001 From: Usha Mandya Date: Fri, 26 Nov 2021 16:10:02 +0000 Subject: [PATCH] Clarify the max-retries option Signed-off-by: Usha Mandya --- 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 7deddd6590..7696d3b0f4 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`(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. | +| `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. |