Dimitri Savineau 2faed4c204 podman: always remove container on start ... In case of failure, the systemd ExecStop isn't executed so the container isn't removed. After a reboot of a failed node, the container doesn't start because the old container is still present in created state. We should always try to remove the container in ExecStartPre for this situation. A normal reboot doesn't trigger this issue and this also doesn't affect nodes running containers via docker. This behaviour was introduced by d43769d. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1858865 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 47b7c00287)		2020-07-24 12:47:01 -04:00
..
node_exporter.service.j2	podman: always remove container on start	2020-07-24 12:47:01 -04:00