想用群晖玩frigate，请问这样的配置可以么？

小来

白群晖，尝试了安装，安装不上，dsm7.2系统。如果不行，请问用什么配置比较好？
还有一台freenas 在，配置如下：

zmqo1234

黑裙按这个配置成功链接

twfjcn

ARM盒子都能玩了,利用NPU还蛮快

小来

hcr-io-blakeblackshear-frigate-1
date        stream        content
2024/03/20 10:44:48        stdout        s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service s6rc-oneshot-runner: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service fix-attrs successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service fix-attrs: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service legacy-cont-init successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service s6rc-fdholder successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service legacy-cont-init: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service log-prepare successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service s6rc-fdholder: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service log-prepare: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc-log successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service frigate-log successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc-log: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service nginx-log successfully stopped
2024/03/20 10:44:48        stdout        2024-03-20 02:44:48.554693147  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024/03/20 10:44:48        stdout        s6-rc: info: service frigate-log: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service frigate successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service frigate: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service nginx-log: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service nginx successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc-healthcheck successfully stopped
2024/03/20 10:44:48        stdout        2024-03-20 02:44:48.502403563  [INFO] Service NGINX exited with code 256 (by signal 15)
2024/03/20 10:44:48        stdout        2024-03-20 02:44:48.498471945  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc-healthcheck: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service nginx: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service legacy-services successfully stopped
2024/03/20 10:44:48        stdout        s6-rc: info: service legacy-services: stopping
2024/03/20 10:44:48        stdout        s6-rc: info: service legacy-services successfully started
2024/03/20 10:44:48        stdout        2024-03-20 02:44:48.433930218  [INFO] Service Frigate exited with code 1 (by signal 0)
2024/03/20 10:44:48        stdout        s6-rc: info: service legacy-services: starting
2024/03/20 10:44:48        stdout        2024-03-20 02:44:48.423685304  [INFO] Starting NGINX...
2024/03/20 10:44:48        stdout        2024-03-20 02:44:48.420601531  [ERROR] Frigate config file not found
2024/03/20 10:44:48        stdout        2024-03-20 02:44:48.420063244  [INFO] Preparing Frigate...
2024/03/20 10:44:48        stdout        s6-rc: info: service nginx successfully started
2024/03/20 10:44:48        stdout        2024-03-20 02:44:48.403708983  [INFO] Preparing new go2rtc config...
2024/03/20 10:44:48        stdout        s6-rc: info: service nginx: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service frigate successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc-healthcheck successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service frigate: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc-healthcheck: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service nginx-log successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service frigate-log successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc-log successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service frigate-log: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service go2rtc-log: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service nginx-log: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service log-prepare successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service log-prepare: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service legacy-cont-init successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service legacy-cont-init: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service fix-attrs successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service s6rc-fdholder successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service fix-attrs: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service s6rc-oneshot-runner successfully started
2024/03/20 10:44:48        stdout        s6-rc: info: service s6rc-oneshot-runner: starting
2024/03/20 10:44:48        stdout        s6-rc: info: service s6rc-fdholder: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service s6rc-fdholder successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service s6rc-oneshot-runner: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service fix-attrs successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service fix-attrs: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service legacy-cont-init successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service legacy-cont-init: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service log-prepare successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service s6rc-fdholder: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service log-prepare: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc-log successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service frigate-log successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc-log: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc successfully stopped
2024/03/20 10:44:40        stdout        2024-03-20 02:44:40.877565040  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024/03/20 10:44:40        stdout        s6-rc: info: service nginx-log successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service frigate-log: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service frigate successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc-healthcheck successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service frigate: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service nginx-log: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service nginx successfully stopped
2024/03/20 10:44:40        stdout        2024-03-20 02:44:40.729128031  [INFO] Service NGINX exited with code 256 (by signal 15)
2024/03/20 10:44:40        stdout        2024-03-20 02:44:40.726909213  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc-healthcheck: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service nginx: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service legacy-services successfully stopped
2024/03/20 10:44:40        stdout        s6-rc: info: service legacy-services: stopping
2024/03/20 10:44:40        stdout        s6-rc: info: service legacy-services successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service legacy-services: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service nginx successfully started
2024/03/20 10:44:40        stdout        2024-03-20 02:44:40.595198214  [INFO] Service Frigate exited with code 1 (by signal 0)
2024/03/20 10:44:40        stdout        2024-03-20 02:44:40.593533173  [INFO] Starting NGINX...
2024/03/20 10:44:40        stdout        s6-rc: info: service nginx: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service frigate successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc-healthcheck successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service nginx-log successfully started
2024/03/20 10:44:40        stdout        2024-03-20 02:44:40.435745665  [ERROR] Frigate config file not found
2024/03/20 10:44:40        stdout        2024-03-20 02:44:40.417957623  [INFO] Preparing Frigate...
2024/03/20 10:44:40        stdout        s6-rc: info: service frigate: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service frigate-log successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc-healthcheck: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc-log successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service frigate-log: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service go2rtc-log: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service nginx-log: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service log-prepare successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service log-prepare: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service legacy-cont-init successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service legacy-cont-init: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service fix-attrs successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service fix-attrs: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service s6rc-oneshot-runner successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service s6rc-fdholder successfully started
2024/03/20 10:44:40        stdout        s6-rc: info: service s6rc-oneshot-runner: starting
2024/03/20 10:44:40        stdout        s6-rc: info: service s6rc-fdholder: starting

复制代码

是白群晖 ，docker运行不断重启

三尺寒

twfjcn 发表于 2024-3-20 10:39
ARM盒子都能玩了,利用NPU还蛮快

你用的什么盒子？

小来

zmqo1234 发表于 2024-3-20 10:31
黑裙按这个配置成功链接

感谢，配置成功了

twfjcn

三尺寒 发表于 2024-3-20 10:53
你用的什么盒子？

git上面就有rk模型

三尺寒

twfjcn 发表于 2024-3-20 14:02
git上面就有rk模型

我的是黑豹X2，不会编译系统，也没找到支持npu的armbian

25989406

[ERROR] Frigate config file not found
你这不是运行不起来，是没有正确的配置文件。。。。日志里稍微看一下知道了