From 26d5df77dfd0b526dac88da5e23c9cdd9ae58dea Mon Sep 17 00:00:00 2001 From: Ygal Blum <ygal.blum@gmail.com> Date: Mon, 20 Mar 2023 09:53:15 +0200 Subject: [PATCH] Quadlet Doc: Suggest the kill operation for HealthOnFailure Co-authored-by: Valentin Rothberg <vrothberg@redhat.com> Signed-off-by: Ygal Blum <ygal.blum@gmail.com> --- docs/source/markdown/podman-systemd.unit.5.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/source/markdown/podman-systemd.unit.5.md b/docs/source/markdown/podman-systemd.unit.5.md index 832fbeb974..86e07d4352 100644 --- a/docs/source/markdown/podman-systemd.unit.5.md +++ b/docs/source/markdown/podman-systemd.unit.5.md @@ -88,7 +88,7 @@ Valid options for `[Container]` are listed below: | Group=1234 | --user UID:1234 | | HealthCmd="/usr/bin/command" | --health-cmd="/usr/bin/command" | | HealthInterval=2m | --health-interval=2m | -| HealthOnFailure=restart | --health-on-failure=restart | +| HealthOnFailure=kill | --health-on-failure=kill | | HealthRetries=5 | --health-retries=5 | | HealthStartPeriod=1m | --health-start-period=period=1m | | HealthStartupCmd="/usr/bin/command" | --health-startup-cmd="/usr/bin/command" | @@ -221,6 +221,9 @@ Equivalent to the Podman `--health-interval` option. ### `HealthOnFailure=` Action to take once the container transitions to an unhealthy state. +The "kill" action in combination integrates best with systemd. Once +the container turns unhealthy, it gets killed and systemd will restart +service. Equivalent to the Podman `--health-on-failure` option. ### `HealthRetries=`