configpolicy/roles/frigate
Dustin eb79f6ea83 r/frigate: Work around podman/netavark lock
Podman 4 puts lock files in the configuration directory for [some stupid
reason][0].  There are so many issues here!

* It is now impossible to run `podman` as root with a read-only `/etc`.
* Why does it need the lock file at all when using `--network=host`?

Luckily, we can work around it fairly easily by mounting a tmpfs
filesystem over the directory it wants to put the lock file in.  This
pretty much defeats the purpose of having a lock file, but it's likely
not needed anyway.

[0]: 836fa4c493
2022-07-23 17:43:54 -05:00
..
defaults r/frigate: Add role to deploy Frigate 2021-08-21 17:16:58 -05:00
handlers r/frigate: Add role to deploy Frigate 2021-08-21 17:16:58 -05:00
tasks r/frigate: Ensure service starts at boot 2021-12-30 09:35:14 -06:00
templates r/frigate: Work around podman/netavark lock 2022-07-23 17:43:54 -05:00
vars r/frigate: Add role to deploy Frigate 2021-08-21 17:16:58 -05:00