The unit already has a ExecStop command that runs 'podman|docker stop',
so systemd should not *also* try to kill the process or else it may
screw up the container state
From https://www.redhat.com/sysadmin/podman-shareable-systemd-services
"Note: It’s important to set the kill mode to none. Otherwise, systemd
will start competing with Podman to stop and kill the container processes.
which can lead to various undesired side effects and invalid states."
Hopefully-fixes: https://tracker.ceph.com/issues/43883
Signed-off-by: Sage Weil <sage@redhat.com>
ExecStartPre=-{container_path} rm ceph-{fsid}-crash
ExecStart={cmd}
ExecStop=-{container_path} stop ceph-{fsid}-crash
+KillMode=none
Restart=always
RestartSec=10
StartLimitInterval=10min
ExecStart=/bin/bash {data_dir}/{fsid}/%i/unit.run
ExecStop=-{container_path} stop ceph-{fsid}-%i
ExecStopPost=-/bin/bash {data_dir}/{fsid}/%i/unit.poststop
+KillMode=none
Restart=on-failure
RestartSec=10s
TimeoutStartSec=120