From d7f0aa6f96c4dd22f53b97a4a1889af1a2a87cc9 Mon Sep 17 00:00:00 2001 From: Erich Blume Date: Tue, 3 Mar 2026 15:18:16 -0800 Subject: [PATCH] Fix Frigate database path to use persistent volume 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 --- argocd/manifests/frigate/frigate-config.yml | 3 +++ docs/changelog.d/main.bugfix.md | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/argocd/manifests/frigate/frigate-config.yml b/argocd/manifests/frigate/frigate-config.yml index 2c15144..baad1e7 100644 --- a/argocd/manifests/frigate/frigate-config.yml +++ b/argocd/manifests/frigate/frigate-config.yml @@ -1,3 +1,6 @@ +database: + path: /db/frigate.db + mqtt: host: mosquitto.mqtt.svc.cluster.local port: 1883 diff --git a/docs/changelog.d/main.bugfix.md b/docs/changelog.d/main.bugfix.md index 43b9286..468096e 100644 --- a/docs/changelog.d/main.bugfix.md +++ b/docs/changelog.d/main.bugfix.md @@ -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