andreas/vanlink
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ha: add Frigate NVR as a Podman Quadlet, wire into deploy.sh

Browse Source 
Same sibling-container pattern as HA/ESPHome. The hand-written unit used
Privileged=true, which isn't a real Quadlet key — the generator silently
drops the whole file on an unsupported key, so frigate.service was never
generated (hence `systemctl enable frigate` saying the unit doesn't exist).
Fixed with PodmanArgs=--privileged.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Andreas Wrede
2026-08-16 21:12:45 -04:00
co-authored by Claude Sonnet 5
parent a4c03496c0
commit b7758c9cd5
2 changed files with 47 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy.sh
+4
View File
@@ -214,6 +214,9 @@ install -d -m0755 /srv/homeassistant
# Supervisor/add-on store here).
install -D -m0644 ha/esphome.container /etc/containers/systemd/esphome.container
install -d -m0755 /srv/esphome
# Frigate NVR (sibling container, same rationale as HA/ESPHome above).
install -D -m0644 ha/frigate.container /etc/containers/systemd/frigate.container
install -d -m0755 /srv/frigate/config /srv/frigate/storage
echo "== hardware watchdog =="
install -D -m0644 power/10-vanlink-watchdog.conf /etc/systemd/system.conf.d/10-vanlink-watchdog.conf
@@ -238,6 +241,7 @@ systemctl enable regdomain.service hostapd hostapd-2g van-ap-dnsmasq nftables sy
systemctl enable --now bluetooth >/dev/null 2>&1 || true
systemctl start homeassistant || warn "homeassistant failed to start (podman/quadlet — check journalctl -u homeassistant)"
systemctl start esphome || warn "esphome failed to start (podman/quadlet — check journalctl -u esphome)"
systemctl start frigate || warn "frigate failed to start (podman/quadlet — check journalctl -u frigate)"
systemctl restart van-thermal
systemctl restart van-nvme-watch
systemctl restart van-gps-owntracks