eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Fix Frigate database path to use persistent volume

Browse source 
The database was at /config/frigate.db (emptyDir, ephemeral) instead of
/db/frigate.db (PVC, persistent). Every pod restart wiped the database,
losing all recording history and leaving orphaned files on NFS.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-03-03 15:18:16 -08:00
commit d7f0aa6f96
2 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
argocd/manifests/frigate/frigate-config.yml
View file

@ -1,3 +1,6 @@
database:
path: /db/frigate.db
mqtt:
host: mosquitto.mqtt.svc.cluster.local
port: 1883

2
docs/changelog.d/main.bugfix.md
View file

@ -1 +1 @@
Trust k3s CNI interfaces (cni0, flannel.1) in ringtail NixOS firewall, fixing pod-to-host networking that broke all ringtail Tailscale Ingress services (authentik, frigate, ntfy, ollama).
Fix Frigate database loss on pod restart by pointing database path to persistent /db volume