[Detector Support]: No EdgeTPU was detected on Proxmox LXC based setup #9970
-
Describe the problem you are havingI'm running frigate in a docker container which is running in an LXC container on proxmox. Whenever frigate tries to use a detector I get logs saying "No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors." and then the container restarts. Version0.13.1-34FB1C2 Frigate config fileffmpeg:
hwaccel_args: preset-vaapi
detectors:
coral:
type: edgetpu
device: usb
#Global Object Settings
objects:
track:
- person
filters:
person:
min_area: 5000
max_area: 100000
go2rtc:
streams:
doorbell:
...
cameras:
doorbell:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
inputs:
- path: rtsp://127.0.0.1:8554/doorbell
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/doorbell_sub
input_args: preset-rtsp-restream
roles:
- detect
- audio
hwaccel_args: preset-vaapi
detect:
enabled: True
record:
enabled: True
snapshots:
enabled: True docker-compose file or Docker CLI commandversion: '3.9'
services:
frigate:
container_name: frigate
privileged: true
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "128mb" # update for your cameras based on calculation above
devices:
- /dev/bus/usb:/dev/bus/usb # for coral usb
- /dev/coral_usb:/dev/coral_usb # coral usb pass through
- /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- /opt/frigate/config:/config
- /mnt/security_camera:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5000:5000"
- "1935:1935" # RTMP feeds
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
environment:
FRIGATE_RTSP_PASSWORD: "foobar" Relevant log outputfrigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Operating systemProxmox Install methodDocker Compose Coral versionUSB Any other information that may be helpfulOn the proxmox host I can see the coral (sometimes as Global Unichip Corp. and sometimes in its Google, Inc.):
I've tried using udev to change some configuration and to assign it a static alias since it changes which usb device number it's listed as. udev is new territory for me, so I don't fully understand what I'm doing here:
LXC container config:
Within the LXC container I can see the coral usb device:
Within the LXC container I'm starting up the frigate docker container with the included docker compose configuration. Within the docker container I can see the coral usb device as well.
In the docker container I don't see /dev/bus/usb/002/004 in the filesystem but I do see dev/coral_usb
The coral always has the same device ID in all three of the proxmox host, the LCX container, and the docker container. I'm not sure how to trigger it to change from one to the other, but I've confirmed that frigate doesn't work in either case. I've also tried running coral python inference code in the docker container. It fails with "Failed to load delegate from libedgetpu.so.1.0 with tflite_runtime" which I understand means its not finding the coral either. I tried to run the same python coral project in the LXC container but my python version there there is too recent and I gave up after spending too long struggling with trying to get a venv or third party wheel to work. If I comment out the detector section from my frigate config it starts up fine and I can see my camera feed. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
this is going to be a proxmox config issue see #9019 (comment) for a similar case |
Beta Was this translation helpful? Give feedback.
this is going to be a proxmox config issue
see #9019 (comment) for a similar case