6 Commits

Author	SHA1	Message	Date
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
Slavi Pantaleev	f3dd346724	Try to tighten Signal bridge security	2021-01-22 18:56:08 +02:00
Slavi Pantaleev	8ec975e3c8	Use matrix:matrix for Signal bridge (not root)	2021-01-22 18:52:20 +02:00
Slavi Pantaleev	37909aa7a9	Create signald/{avatars,attachments,data} and rename config dir	2021-01-22 18:40:51 +02:00
Slavi Pantaleev	1692a28fe4	Work around annoying Docker warning about undefined $HOME ... > WARNING: Error loading config file: .dockercfg: $HOME is not defined .. which appeared in Docker 20.10.	2021-01-15 00:23:01 +02:00
Sabine	69efcb5c21	added mautrix-signal role	2020-10-22 23:29:34 +02:00