Valentin Rothberg 274d6fa19c generate systemd: use --cidfile again ...

Commit 9ac5267 changed the type of the generated systemd units from
`forking` to `notify`.  It further stopped using `--cidfile` and instead
intended systemd to take care of stopping the container, which turned
out to be a bad idea.

Systemd will send the stop/kill signals to conmon which in turn may exit
non-zero, depending on the signal, and ultimately breaking container
cleanup.

Hence, we need to use --cidfile again and let podman stop and remove the
container to make sure that everything's in order.

Fixes: #11304
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>

2021-08-24 15:46:00 +02:00

..

common_test.go

generate systemd: use --cidfile again

2021-08-24 15:46:00 +02:00

common.go

generate systemd: use --cidfile again

2021-08-24 15:46:00 +02:00

containers_test.go

generate systemd: use --cidfile again

2021-08-24 15:46:00 +02:00

containers.go

generate systemd: use --cidfile again

2021-08-24 15:46:00 +02:00

pods_test.go

Revert "generate systemd: custom stop signal"

2021-08-24 13:33:06 +02:00

pods.go

Revert "generate systemd: custom stop signal"

2021-08-24 13:33:06 +02:00