automation-tests/cmd/podman/common
Valentin Rothberg aad29e759c health check: add on-failure actions
For systems that have extreme robustness requirements (edge devices,
particularly those in difficult to access environments), it is important
that applications continue running in all circumstances. When the
application fails, Podman must restart it automatically to provide this
robustness. Otherwise, these devices may require customer IT to
physically gain access to restart, which can be prohibitively difficult.

Add a new `--on-failure` flag that supports four actions:

- **none**: Take no action.

- **kill**: Kill the container.

- **restart**: Restart the container.  Do not combine the `restart`
               action with the `--restart` flag.  When running inside of
               a systemd unit, consider using the `kill` or `stop`
               action instead to make use of systemd's restart policy.

- **stop**: Stop the container.

To remain backwards compatible, **none** is the default action.

Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
2022-09-09 13:02:05 +02:00
..
completion.go health check: add on-failure actions 2022-09-09 13:02:05 +02:00
completion_test.go golangci-lint: enable nolintlint 2022-06-14 16:29:42 +02:00
create.go health check: add on-failure actions 2022-09-09 13:02:05 +02:00
create_opts.go podman pod clone 2022-06-10 14:23:19 -04:00
create_test.go linter: enable unconvert linter 2022-05-19 13:59:15 +02:00
default.go Support setting image_volume_mode in containers.conf 2022-05-26 14:16:26 -04:00
diffChanges.go cmd/podman: switch to golang native error wrapping 2022-06-30 12:58:57 +02:00
inspect.go fix podman pod inspect to support multiple pods 2022-09-08 10:28:42 +02:00
netflags.go Add Docker compatibility for --dns-option to --dns-opt 2022-08-15 07:38:08 -04:00
sign.go podman ssh work, using new c/common interface 2022-08-09 14:00:58 -04:00