administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-10-11 17:22:49 +03:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

tolerate homekit config chown failures in the go2rtc run script

Browse Source
This commit is contained in:
Josh Hawkins
2026-08-23 18:26:13 -05:00
parent fa191b0faa
commit 78e39e7a22
2 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker/main/rootfs/etc/s6-overlay/s6-rc.d/go2rtc/run
+5 -3
View File
@@ -113,9 +113,11 @@ setup_homekit_config "${homekit_config_path}"
if [[ "$(id -u)" -eq 0 && "${FRIGATE_RUN_AS_ROOT:-false}" != "true" ]]; then
chown go2rtc:go2rtc /dev/shm/go2rtc.yaml 2>/dev/null || true
# go2rtc rewrites this in place (os.WriteFile, no rename), so owning the
# file is enough; /config grants frigate-data traverse only
chown go2rtc:frigate-data "${homekit_config_path}"
chmod 664 "${homekit_config_path}"
# file is enough; /config grants frigate-data traverse only. Tolerated so
# a chown-refusing mount (NFS root_squash) degrades pairing persistence
# instead of crash-looping the service
chown go2rtc:frigate-data "${homekit_config_path}" 2>/dev/null && chmod 664 "${homekit_config_path}" 2>/dev/null || \
echo "[WARN] Could not hand ${homekit_config_path} to the go2rtc user; HomeKit pairing changes may not persist"
fi
readonly config_path="/config"