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
..
custom-sip-communicator.properties.j2	Update Jitsi to build 5142	2020-11-27 17:57:15 +02:00
env.j2	Update Jitsi to build 5142	2020-11-27 17:57:15 +02:00
logging.properties.j2	Manage Jitsi configuration by ourselves for most components	2020-03-24 09:35:21 +02:00
matrix-jitsi-jvb.service.j2	Do not report docker kill/rm attempts as errors	2021-01-27 10:22:46 +02:00