Problem with frigate in docker on OMV

RLB7777 · May 7th 2025

Hi, I'm new to OMV and also docker, and I'm struggling with my Frigate install. Could someone tell me what I'm doing wrong?

OMV is running fine. I have installed the compose plugin, which also seems fine. I have a dedicated SSD for the docker shared folders (appdata, backup_compose, docker). I've installed Frigate using the example config, adapted for my setup, and that works. I've logged into the web UI for Frigate, and configured my cameras there. Again, that all works.

However, when I look in the appdata shared folder, I have a config sub-folder but it is empty (the Frigate compose file is there, in the root). The config must exist somewhere - when I edit it in the web UI it says it is being saved. And if I trigger a backup of docker (manually triggering the scheduled task) it brings down Frigate, before it backs up and then pushes Frigate up. If the config was only in RAM I assume it would restart without any of my camera configuration, but it seems fine. However, this means:

- I don't have any backup of the frigate config (in the backup compose folder it has the modified Frigate compose file, the recordings etc but the backup of the config directory is empty)

- I can't edit the config.yml for outside of the web UI (not that I care much about that)

Right now I'm manually taking a copy of the Frigate config out of the web UI in notepad so I can rebuild everything if it goes down. But I assume that's not how it's meant to work.

I've searched the forum and see that there was a problem in the past where the config directory file path was wrong in the example compose, result in a config folder being created but not a yml file. But that seemed to manifest as Frigate not starting at all. My instance of Frigate works fine. And in any case, my file path seems correct.

Code

${PATH_TO_APPDATA}/frigate/config:/config/config

Can someone provide some guidance? I assume the yml file must exist somewhere otherwise I wouldn't be able to take Frigate down and bring it back up? But I can't see it, and can't back it up. Maybe I just don't understand how docker works, or Frigate works. Or maybe I've made some rookie error. But this doesn't seem right to me.

Thanks in advance for any guidance.

Zafkiel · May 7th 2025

Quote from RLB7777

${PATH_TO_APPDATA}/frigate/config:/config/config

I guess there might be an extra /config on the right side of your volume mapping.

RLB7777 · May 7th 2025

Thanks for this. I'm out now and can't remote in, but when I get home I'll try this and let you know.

RLB7777 · May 11th 2025

Quote from Zafkiel

I guess there might be an extra /config on the right side of your volume mapping.

I just wanted to let you know you are correct. Removing the second config got it all working. Thanks very much for your help. That does mean it's incorrect in the Frigate "add by example" file. How can I get that changed so others don't have the same issue?

chente · May 11th 2025

Indeed. Looking at the Frigate installation page: https://docs.frigate.video/frigate/installation

And comparing with the code in the plugin example file:

Code

---
# https://github.com/blakeblackshear/frigate
services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "64mb" # update for your cameras based on calculation above
    devices:
      - /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions
      - /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
      - /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - CHANGE_TO_COMPOSE_DATA_PATH/frigate/config:/config/config
      - CHANGE_TO_COMPOSE_DATA_PATH/frigate/storage:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      # - "5000:5000" # Internal unauthenticated access. Expose carefully.
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
      - "8971:8971"
    environment:
      FRIGATE_RTSP_PASSWORD: "password"

Display More

There seems to be an error in this file.

I'll mention ryecoaaron here so he can see it when he's active. He's currently unable to access the forum for personal reasons.

ryecoaaron · May 19th 2025

I don't even know what frigate is. That example was submitted by trythat but it does look like /config is doubled.

trythat · May 19th 2025

I apologize, I'm sure when I submitted the example, I took it from Github, but that was a few versions ago, I'm on beta 16 branch now.

There have been quite a few breaking changes since I submitted it.

Rycoarron, if you can provide the list of files I submitted, I'll go and check them against what is recommended now, and change them, make sure I add a date and the original project page..

Perhaps going forward the submitter can add the date they were submitted, and the project/container page they got them from? Then people can always go to the go the project page and do a sanity check themselves.

ryecoaaron · May 19th 2025

Quote from trythat

if you can provide the list of files I submitted, I'll go and check them against what is recommended now, and change them, make sure I add a date and the original project page..

I would have to go back through commit history and look for large group of commits. I don't have time to do that now.

Quote from trythat

Perhaps going forward the submitter can add the date they were submitted, and the project/container page they got them from? Then people can always go to the go the project page and do a sanity check themselves.

The date might be helpful. I have always put the project on the compose files I created - https://github.com/OpenMediaVa…es/firefox/firefox.yml#L2

trythat · May 20th 2025

Quote from ryecoaaron

I would have to go back through commit history and look for large group of commits. I don't have time to do that now.

OK, I've found the list and grabbed it, so I can see what I might have sent you. I'll make time to try and go through the list and add dates and try and check against what is the recommendations now, will take me some time though.

Jack@007 · May 21st 2025

Problem with frigate in docker on OMV

ryecoaaron May 7th 2025

Participate now!

Similar Threads

Noob help; Running Frigate

Tags