Dimitri Savineau d408c75d76 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:21 -04:00
..
alertmanager.service.j2	podman: always remove container on start	2020-07-24 12:47:21 -04:00
alertmanager.yml.j2	dashboard: use fqdn url for active alert	2019-12-03 09:44:17 -05:00
prometheus.service.j2	podman: always remove container on start	2020-07-24 12:47:21 -04:00
prometheus.yml.j2	Add http_addr option to grafana config	2019-08-30 09:04:16 -04:00