solved - Frigate with Docker and Coral TPU

snobby · February 22, 2025 at 3:08 PM

Hello, I have installed Docker and also frigate. Its working fine with detector cpu, but now I got also an USB Coral TPU.

The TPU is found in the host as:

Code

root@DXP2800-A136:~# lsusb
Bus 004 Device 015: ID 18d1:9302 Google Inc.

So i added the device in the docker compose as followed:

Code

devices:
- /dev/bus/usb//004/015 # Passes the USB Coral

and the config.yaml

YAML

detectors:
coral:
type: edgetpu
device: usb

It seems to work, but I still get the following error messages:

Code

2025-02-22 15:00:06.277717349 [2025-02-22 15:00:03] detector.coral INFO : Starting detection process: 422
2025-02-22 15:00:06.277886619 [2025-02-22 15:00:03] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb
2025-02-22 15:00:06.278527292 [2025-02-22 15:00:06] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found
2025-02-22 15:00:06.278670378 [2025-02-22 15:00:06] frigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.

Anyone here who already is using an DXP2800 with docker and frigate/Coral USB TPU?

Any idea what I can do to solve the problem?

Best regards, Stefan

Mike0185 · February 22, 2025 at 8:58 PM

Hi Stefan,

welcome to our Community!

I have a DXP2800 and also a Google Coral USB TPU. Can you provide me your container stack? Then I can maybe test it next week.

Regards Mike

snobby · February 22, 2025 at 11:11 PM

Dear Mike,

this is my Frigate container:

YAML

version: "3.9"
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
stop_grace_period: 30s # allow enough time to shut down the various services
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "512mb" # update for your cameras based on calculation above
devices:
- /dev/bus/usb//004/015 # 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/video11:/dev/video11 # For Raspberry Pi 4B
# - /dev/dri/renderD128:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- /volume3/docker/frigate/config:/config:rw
- /volume5/frigate/media:/media/frigate:rw
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "8971:8971"
- "5000:5000" # Internal unauthenticated access. Expose carefully.
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp

Display More

It would be great if you can find a solution. I am using the Coral TPU in the front USB port. In which port do you have it connected?

Best regards, Stefan

wasawasa · February 24, 2025 at 6:14 PM

- /dev/bus/usb//004/015 # Passes the USB Coral, needs to be modified for other versions

Something might be missing here.

- /dev/bus/usb//004/015:/dev/bus/usb//004/015 # Passes the USB Coral, needs to be modified for other versions

snobby · February 24, 2025 at 9:30 PM Best Answer

I got it. It´s solved !!!

Yesterday I found out that the usb was passed through, but the configuration did not recognize the coral tpu. And due to the fact that the number of the device mounted after each reboot 004/016, 004/017 ... I changed the setting in the settings in the composer now to.

devices:

- "/dev/bus/usb/004:/dev/bus/usb/004"

# /dev/bus/usb//004 # Passes the USB Coral, needs to be modified for other versions

In order to get the tpu module running I tried chatgpt for help and reinstalled the module again via telnet to the ugreen and by running the installation for debian. I still had some problems with duplicate lines in the config files, which I realized by uploading the log to chatgpt. When I deleted the duplicate lines the installation finished and now the TPU is recognized, the cpu dropped from 80% (8 cameras) to nearly 25%.

In the next days I will need to optimize the setup of all the cameras and the different resolutions, then the integration with HA can start.

Thanks to everyone trying to help.

Best regards, Stefan

Mike0185 · March 14, 2025 at 9:48 AM

Ich hatte jetzt auch mal Zeit den Google Coral an einer DXP2800 mit Frigate zu testen:

SSH: lsusb

Code

root@DXP2800:~# lsusb
Bus 004 Device 003: ID 18d1:9302 Google Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

YAML

version: "3.9"
services:
 frigate:
   container_name: frigate
   restart: unless-stopped
   stop_grace_period: 30s  # Allow enough time to shut down the various services
   image: ghcr.io/blakeblackshear/frigate:stable
   shm_size: "512mb"  # Update for your cameras based on calculation above
   privileged: true  # Falls der Coral nicht erkannt wird, kannst du es testweise auf "true" setzen.
   
   devices:
     - /dev/bus/usb:/dev/bus/usb  # Erlaubt Frigate Zugriff auf den Coral (kein fester Pfad nötig!)
     # - /dev/apex_0:/dev/apex_0  # Falls PCIe-Coral genutzt wird, diesen Eintrag aktivieren
   environment:
     - FRIGATE_RTSP_PASSWORD=dein_passwort  # Falls RTSP genutzt wird, ersetze es mit deinem Passwort
   volumes:
     - /etc/localtime:/etc/localtime:ro
     - /volume2/docker/frigate/config:/config:rw
     - /volume1/frigate:/media/frigate:rw
     - type: tmpfs
       target: /tmp/cache
       tmpfs:
         size: 1000000000  # 1GB of memory, reduces SSD/SD Card wear
   ports:
     - "8971:8971"
     - "5000:5000"  # Internal unauthenticated access. Expose carefully.
     - "8554:8554"  # RTSP feeds
     - "8555:8555/tcp"  # WebRTC over TCP
     - "8555:8555/udp"  # WebRTC over UDP
   deploy:
     resources:
       limits:
         memory: 4G  # Adjust as needed
       reservations:
         memory: 512M  # Minimum required memory

Display More

In der Config-YAML von Frigate folgendes ergänzt:

YAML

detectors:
  coral:
    type: edgetpu
    device: usb

Portainer-Log:

Code

frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb2025-03-14
frigate.app                    INFO    : Output process started: 
frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found

This image is exclusive to our members!
Please log in or register for free to view graphics and attachments.

VG
Mike

foltz61 · September 6, 2025 at 5:35 PM

Can anyone tell me how can I add the Coral USB using the built in docker app? Thanks in advance for any help.

Mike0185 · September 9, 2025 at 7:46 AM

You can’t just “add” the Coral USB accelerator to a container in most NAS GUIs without explicitly mapping it through to Docker. You basically need to do two things:

1. Make sure your NAS sees the Coral USB device, SSH: lsusb

2. Pass the USB device to your container. In Docker CLI this is done with --device, for example:

--device /dev/bus/usb/001/002:/dev/bus/usb/001/002 ...

or Stack:

YAML

devices:
     
  - /dev/bus/usb:/dev/bus/usb

foltz61 · September 9, 2025 at 5:33 PM

I was specifically talking about doing it via GUI but it doesn't matter now. I've installed portainer and got everything I need done so far.

For anyone searching, I was setting up the Google Cotal TPU with frigate. I have the container running in privileged mode so the Coral was automatically detected after its initialization. with mo device settings meeded in rhe docker config

Here's info about initialization. of th Coral

https://docs.frigate.video/troubleshooting/edgetpu

solved - Frigate with Docker and Coral TPU

Participate now!

Tags