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
..
define	Do not leak libpod package into the remote client	2021-03-15 14:02:04 +01:00
generate	generate systemd: use --cidfile again	2021-08-24 15:46:00 +02:00
activation.go	pkg/systemd: don't require LISTEN_FDNAMES for socket activation	2021-06-24 09:01:39 -06:00
activation_test.go	pkg/systemd: don't require LISTEN_FDNAMES for socket activation	2021-06-24 09:01:39 -06:00
dbus.go	cgroup-manager-systemd:Fail early if user:rootless and relevent session is not present.	2021-08-17 16:18:54 +05:30