Valentin Rothberg 8228182875 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.

Backport of commit 74ab2aaf9f.

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

2021-08-25 10:08:41 +02:00

..

common_test.go

generate systemd: use --cidfile again

2021-08-25 10:08:41 +02:00

common.go

generate systemd: use --cidfile again

2021-08-25 10:08:41 +02:00

containers_test.go

generate systemd: use --cidfile again

2021-08-25 10:08:41 +02:00

containers.go

generate systemd: use --cidfile again

2021-08-25 10:08:41 +02:00

pods_test.go

systemd: require network*-online*.target

2021-07-16 14:58:08 +02:00

pods.go

podman generate systemd --new do not duplicate params

2021-03-28 20:01:17 +02:00