Does it work with DSM6 too?

[ruberwm]

Hi,
I have a ds1515+ still on DSM6 at the moment.
I want to move to DSM7 eventually but right now I need to stick to 6 and I'd like to install frigate.
I am looking for a stable version of frigate.

Does this version work with DSM6 too?
If yes, generally speaking (dsm7 and 6) what happens in case I restart the nas? Does frigate restart automatically or do I need to manually (or by a task schedule) do something?
I know that docker automatically restarts and I have other apps on docker that restart flawlessly, I am not sure about frigate. :)

Thank you. Have a nice day.

[weltenwort]

Hi @ruberwm 👋

Does this version work with DSM6 too?

I don't have any way to test with DSM6 myself, but the comment in blakeblackshear/frigate#2426 (reply in thread) suggests that it works even without the fix that this image adds. Maybe the DSM6 kernel has been compiled with udev support. 🤷

[...] generally speaking (dsm7 and 6) what happens in case I restart the nas?

For me (on DSM7) the docker engine automatically starts the container again after boot, so no manual intervention is required.

[ruberwm]

Thank you @weltenwort :)

I don't have any way to test with DSM6 myself, but the comment in blakeblackshear/frigate#2426 (reply in thread) suggests that it works even without the fix that this image adds. Maybe the DSM6 kernel has been compiled with udev support. 🤷

Ok, since I'd like to move to DSM7 and I'd like to keep consinstency, I'll give a try with your image :)

For me (on DSM7) the docker engine automatically starts the container again after boot, so no manual intervention is required.

Perfect!

[weltenwort]

let me know how it works out on DSM6

[Floriszz]

I run Frigate latest stable(0.11.1-2EADA21) on my Synology NAS DS918+ with DSM6x(latest) and Google Coral USB stick flawless for couple of months now. (waiting on Frigate 0.12.x stable before moving to DSM 7.x)
I don't use cli/ssh and/or Docker compose. Just the Docker run commands through DSM Task Scheduler to install/run/update.
After reboot or cold start(we had power outage last week) everything comes up automatically.

[mx-vatte]

The installation by DSM task scheduler seems to work but the container kills with the following protocol.

docker run -d
--name frigate
--restart=unless-stopped
--mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000
--device /dev/bus/usb:/dev/bus/usb
--shm-size=128m
--privileged
-v /volume1/docker/frigate/storage:/media/frigate
-v /volume1/docker/frigate/config.yml:/config/config.yml:ro
-v /etc/localtime:/etc/localtime:ro
-v /dev/bus/usb:/dev/bus/usb
-v /volume1/docker/frigate/db:/db
-e FRIGATE_RTSP_PASSWORD='1234567890'
-p 5055:5055
-p 1935:1935
blakeblackshear/frigate:stable

`

2023-03-22T16:29:56.174429598Z	stdout	[cont-finish.d] done.
2023-03-22T16:29:56.174001546Z	stdout	[cont-finish.d] executing container finish scripts...
2023-03-22T16:29:56.140310191Z	stdout	[cmd] \ exited 127
2023-03-22T16:29:56.138940334Z	stderr	ifelse: fatal: unable to exec : No such file or directory
2023-03-22T16:29:56.110303756Z	stdout	[services.d] done.
2023-03-22T16:29:56.094226713Z	stdout	[services.d] starting services
2023-03-22T16:29:56.093529609Z	stdout	[cont-init.d] done.
2023-03-22T16:29:56.092960856Z	stdout	[cont-init.d] executing container initialization scripts...
2023-03-22T16:29:56.092354763Z	stdout	[fix-attrs.d] done.
2023-03-22T16:29:56.091746270Z	stdout	[fix-attrs.d] applying ownership & permissions fixes...
2023-03-22T16:29:56.090860035Z	stdout	[s6-init] ensuring user provided files have correct perms...exited 0.
2023-03-22T16:29:56.061358953Z	stdout	[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

`

Any idea where I've made a mistake?

[Floriszz]

Did you create 3 folders for the Docker image on you nas under the ' frigate' folder?

[mx-vatte]

I tried different structures already. Everytime the same error.

[Floriszz]

@mx-vatte , seems you run in the same issue I broke my head over for weeks, why I could not get the container to stay running.
Check the ports you configured! The second port is the internal port for the container. You are not supposed to change this port.
It should be 5000! See my example

[Floriszz]

Also check where you put the config.yml.
In your example with; -v /volume1/docker/frigate/config.yml:/config/config.yml:ro
the config.yml should be in the root of the 'frigate' folder. If you want the file in a folder 'config' it should be;
-v /volume1/docker/frigate/config/config.yml:/config/config.yml:ro or
-v /volume1/docker/frigate/storage/config/config.yml:/config/config.yml:ro

[mx-vatte]

Thx for your reply. In the meantime I got frigate running by the standard way with SSH onto the Diskstation. Just waiting for the coral stick to arrive to implement more cameras. The absolute basics are explained in this discussion.

I think with my knowledge now and though the right config etc. It would also run by DSM task scheduler method.

[Floriszz]

thanks for the link. I think we can help others while using the task scheduler is super easy and saver compared to enable SSH and using command line commands.
So I posted my suggestion in the link you shared above. Hopefully it will be added to the general documentation of Frigate and can help many others.
So happy with the Object recognition instead of the motion sensing only in/with Surveillance station.