The source thread is an introduction to an external 2023 tutorial, not a complete Frigate deployment record. It says the tutorial will install Frigate on CasaOS and integrate cameras with Google Coral, but it does not preserve the Docker image, volumes, ports, shared-memory size, or detector configuration used at the time.
For a current setup, Frigate's maintained documentation should be the technical baseline. Docker Compose remains the recommended installation method, and Google Coral is now only one hardware-acceleration option among several possible detector/video paths.
Current Frigate Recommends Docker Compose
Frigate's current installation guide uses ghcr.io/blakeblackshear/frigate:stable, persistent configuration/media, an explicit shared-memory size, and device mappings appropriate to the selected accelerator.
Use the current Frigate installation model instead of copying a 2023 video verbatim.
Persist /config Outside the Container
Frigate's YAML configuration belongs in a host folder mapped to /config. Keep it on persistent CasaOS storage so container recreation does not erase camera, detector, recording, zone, and snapshot settings.
Map Recordings and Clips to Real Storage
NVR video can grow much faster than ordinary AppData. Put recordings, clips, and exports on a storage volume with enough capacity rather than the small OS disk.
Shared Memory Must Match the Camera Workload
Frigate uses shared memory for video processing. The current Compose example includes an explicit shm_size, and the correct value depends on camera resolution and count.
Google Coral Is Optional, Not a Universal Requirement
The 2023 source emphasized Google Coral. Current Frigate still documents USB and PCIe Coral mappings, but modern deployments may also use Intel/AMD video acceleration, Intel NPU, or other supported detector paths depending on hardware.
Hardware Acceleration Requires the Correct Device Mapping
Current examples include /dev/bus/usb for USB Coral, /dev/apex_0 for PCIe Coral, /dev/dri/renderD128 for Intel/AMD graphics, and /dev/accel for supported Intel NPU paths. Grant only the hardware Frigate actually needs.
Privileged Mode Is Not Always Required
Frigate's current Compose example notes that privileged: true may not be necessary for all setups. Least privilege is preferable when explicit device mappings and permissions are enough.
Keep Camera Credentials and RTSP Endpoints Private
Frigate configuration commonly contains camera usernames, passwords, and RTSP URLs. Avoid publishing complete config files or screenshots without redacting secrets, and avoid exposing RTSP directly to the Internet.
CasaOS Is the Container Host, Not the Frigate Configuration Layer
CasaOS can launch the container and map storage/devices, while Frigate's YAML controls NVR behavior. If the app opens but cameras fail, inspect Frigate logs/configuration rather than repeatedly reinstalling CasaOS.
Object Detection and Video Decoding Are Different Acceleration Jobs
A Coral accelerator is used for supported object-detection inference; Intel/AMD/NVIDIA video hardware can accelerate decode/encode. One does not automatically replace the other.
Design the Frigate stack around both the detector workload and the camera codec/transcode workload rather than treating “hardware acceleration” as one checkbox.
Set Retention Before Enabling Many Cameras
Continuous recording can fill disks quickly. Estimate bitrate × camera count × retention days, leave filesystem headroom, and decide which events need long retention versus rolling footage.
Check Frigate Logs and Health After the First Start
Before adding every camera, validate one stream, confirm the detector/device is recognized, and review container logs for shared-memory, FFmpeg, or permission errors. Scaling one known-good camera is easier than debugging five simultaneous failures.
Frigate on CasaOS FAQ
Does the original Community post contain the full Frigate Compose file?
No. It mainly points to an external 2023 tutorial.
Is Google Coral mandatory for current Frigate?
No. Coral remains one supported option, but current Frigate supports other hardware paths depending on the host.
What should always be persistent?
At minimum, Frigate configuration and the media/recording storage you want to retain.
