Computing/Frigate: Difference between revisions
From Cricalix.Net
(Created page with "Coral support When running in Incus, two different USB IDs need to be passed through - the Coral device initially shows up as one vendor/product, and then switches to another. If only the first is passed through, Frigate's libraries will initialize the device and then it vanishes from the container.<syntaxhighlight lang="yaml"> devices: coral-google: productid: '9302' type: usb vendorid: 18d1 coral-raw: productid: 089a type: usb vendorid: 1a6...") |
mNo edit summary |
||
| Line 19: | Line 19: | ||
type: disk | type: disk | ||
</syntaxhighlight>Note that the /dev/shm has to be done with the yaml config or CLI; the LXC/D web UI that can be attached to Incus is not aware of the extra values when adding a disk. | </syntaxhighlight>Note that the /dev/shm has to be done with the yaml config or CLI; the LXC/D web UI that can be attached to Incus is not aware of the extra values when adding a disk. | ||
[[File:Dev shm config.png|thumb]] | [[File:Dev shm config.png|thumb|left]] | ||
Revision as of 06:20, 30 April 2026
Coral support
When running in Incus, two different USB IDs need to be passed through - the Coral device initially shows up as one vendor/product, and then switches to another. If only the first is passed through, Frigate's libraries will initialize the device and then it vanishes from the container.
devices:
coral-google:
productid: '9302'
type: usb
vendorid: 18d1
coral-raw:
productid: 089a
type: usb
vendorid: 1a6e
There's also a need to set a larger shared memory space.
devices:
shm:
path: /dev/shm
size: 256MiB
source: 'tmpfs:'
type: disk
Note that the /dev/shm has to be done with the yaml config or CLI; the LXC/D web UI that can be attached to Incus is not aware of the extra values when adding a disk.
