Slavi Pantaleev 512f42aa76 Do not report docker kill/rm attempts as errors ... These are just defensive cleanup tasks that we run. In the good case, there's nothing to kill or remove, so they trigger an error like this: > Error response from daemon: Cannot kill container: something: No such container: something and: > Error: No such container: something People often ask us if this is a problem, so instead of always having to answer with "no, this is to be expected", we'd rather eliminate it now and make logs cleaner. In the event that: - a container is really stuck and needs cleanup using kill/rm - and cleanup fails, and we fail to report it because of error suppression (`2>/dev/null`) .. we'd still get an error when launching ("container name already in use .."), so it shouldn't be too hard to investigate.		2021-01-27 10:22:46 +02:00
..
matrix-nginx-proxy.service.j2	Do not report docker kill/rm attempts as errors	2021-01-27 10:22:46 +02:00
matrix-ssl-lets-encrypt-certificates-renew.service.j2	Work around annoying Docker warning about undefined $HOME	2021-01-15 00:23:01 +02:00
matrix-ssl-lets-encrypt-certificates-renew.timer.j2	Replace cronjobs with systemd timers	2021-01-14 23:35:50 +02:00
matrix-ssl-nginx-proxy-reload.service.j2	Replace cronjobs with systemd timers	2021-01-14 23:35:50 +02:00
matrix-ssl-nginx-proxy-reload.timer.j2	Replace cronjobs with systemd timers	2021-01-14 23:35:50 +02:00