Frigate Docker deployment planning
Docker Compose is the recommended Frigate installation method, but a reliable Docker host still needs deliberate hardware and storage choices. The container must be able to reach the video-decoding device and detector, /config must persist, recordings need a correctly sized /media/frigate path, and shared memory must be set for the camera workload. This guide places current compact hosts, SSDs and UPS products near the top, then works through the deployment details that matter after the container image itself has been chosen.
Quick answer
What this Frigate workload needs
For a dedicated Frigate Docker host, start with a modern Intel or comparable CPU that supports the intended hardware-decoding path, 8–16 GB RAM for a normal multi-camera installation, SSD storage for the host and /config, and a separately sized recording volume. Map only the hardware devices and ports you actually need, calculate shared memory from the current Frigate guidance, and keep enough RAM outside the container for the operating system.
Live Amazon hardware
Current products that fit this decision
Compare current Amazon listings relevant to this guide. Product availability and prices can change.
Buying decision
Match the hardware to the bottleneck
Choose a host that makes hardware access straightforward. A cheaper box is a poor buy if its iGPU, detector interface, storage expansion or Ethernet is awkward under Linux. Docker simplifies application management; it does not remove the need to verify the physical platform.
Interactive decision tool
Frigate Docker Host Planner
Use the workload inputs to size a practical Frigate hardware tier before comparing live products. Results are planning guidance; verify current Frigate support, camera bitrates and the exact hardware configuration before deployment.
Compatibility checklist
Four checks before you purchase
Keep live products near the decision
Current Amazon listings appear above the long guide so capacity, interfaces and prices can be checked before deep reading.
Measure the real workload
Use camera bitrate, retention, PoE draw and network aggregation instead of relying on fixed per-camera rules.
Separate application and recording storage
Keep the Frigate configuration/database role distinct from bulk video retention so each storage tier can be sized correctly.
Verify the complete data path
Camera, switch, NVR, storage and UPS are one recording system; a weak link anywhere can affect reliability.
Docker Compose is Frigate's recommended install path
Current Frigate installation documentation recommends Docker with Docker Compose. That gives a predictable container image, explicit device mappings and clear storage mounts while keeping the host operating system relatively simple. For a dedicated NVR, this is usually easier to operate than adding a hypervisor first. Keep the compose file, configuration and recovery notes under versioned or backed-up management so the host can be rebuilt without recreating the setup from memory.
Choose a Linux host with clean hardware access
The best Docker hardware is not merely the cheapest mini PC that can run containers. Frigate benefits from direct access to Intel, AMD or NVIDIA video acceleration and may also need a detector device. Verify Linux driver support, /dev/dri or other device visibility, BIOS settings and the physical interface for the detector. A simple Debian-based host with well-supported hardware is often more reliable than a novel platform with higher benchmark scores.
Map video acceleration devices explicitly
Hardware decoding reduces CPU load, but Docker must be allowed to access the relevant device. Frigate examples commonly map /dev/dri/renderD128 for Intel/AMD graphics, with different mappings for other accelerators. The exact path depends on the host. Confirm hardware acceleration in Frigate logs and metrics rather than assuming that installing on an Intel CPU automatically enables Quick Sync inside the container.
Treat the detector as a second hardware path
Video decoding and object detection are separate jobs. A system can have working iGPU decoding while its Hailo, Coral, NPU or GPU detector is inaccessible to Docker. Map and test the detector independently. When the accelerator requires a kernel driver or manager service, install the supported version on the host and confirm permissions before adding every camera.
Calculate shared memory instead of copying a random value
Frigate uses shared memory for decoded camera frames, and its installation documentation provides a calculation for sizing shm_size based on resolution and camera count. Use the current official formula rather than copying 64 MB or 512 MB from an unrelated compose file. Too little shared memory can cause failures; unnecessarily huge values simply hide that the workload was never calculated.
Persist /config on reliable SSD storage
The /config mount contains Frigate configuration and the sqlite database. Put it on a persistent host path or volume that is easy to back up and restore. SSD storage is a good fit because the database and host stack benefit from low latency. Do not keep important configuration only inside an ephemeral container layer that disappears when the container is recreated.
Map /media/frigate to deliberately sized storage
Recordings, clips and snapshots need a persistent volume with enough capacity for the retention plan. That may be a local surveillance HDD, SSD or carefully engineered network share. Keep the mapping obvious in the compose file so an administrator can see exactly where footage lives. Avoid letting a default root filesystem silently fill because the recording mount was missing or failed to attach.
Use tmpfs cache intentionally
Frigate installation examples use a tmpfs mount for /tmp/cache. RAM-backed cache can reduce unnecessary disk I/O, but it also consumes memory that must be included in host sizing. The right size depends on the workload. Monitor memory pressure after deployment and do not assume a large tmpfs is free simply because it does not appear in disk usage.
Expose only the ports the deployment requires
Frigate, go2rtc RTSP restream and WebRTC can use several ports. Docker bridge mode requires the relevant mappings, while host networking changes the exposure model. Publish only what the local integration or remote-view design requires. Avoid opening service ports to the public internet as a shortcut; use an appropriate secure remote-access architecture.
Give the container time to stop cleanly
Frigate's Compose example includes a stop grace period because several services need time to shut down. A UPS and clean host shutdown help protect the database and filesystem during power loss. Configure automatic restart for normal operation, but also make sure the system can stop gracefully during planned maintenance or extended outages instead of relying on repeated hard power cuts.
Keep container and host versions compatible
Frigate releases can change driver, detector or configuration requirements. Before major upgrades, read the current release and installation notes, preserve the configuration, and avoid simultaneous OS, driver and application changes when possible. A stable NVR benefits from controlled updates more than from running every new package immediately after release.
Prove one complete camera path first
Before adding 16 cameras, configure one camera through the final Docker network, hardware decoder, detector, recording mount and live-view path. Confirm low CPU decoding, successful detections and retained recordings. Then scale the configuration. This turns deployment into a repeatable pattern and prevents one fundamental mount or permission mistake from being replicated across the entire system.
Questions people ask
Frigate Docker Hardware Guide FAQs
Is Docker Compose the recommended way to install Frigate?
Yes. Current Frigate installation documentation says Docker with Docker Compose is the recommended install method.
How much RAM does Frigate Docker need?
It depends on cameras and enrichments. Many practical systems start around 8 to 16 GB of host RAM, with heavier features requiring more.
What should be stored in /config?
Frigate uses /config for its configuration and sqlite database. Map it to persistent, backed-up storage.
Where should Frigate recordings be mounted?
Frigate uses /media/frigate for recording-related storage. Map it to a deliberately sized persistent volume.
How large should shm_size be?
Use the current Frigate shared-memory calculation based on camera resolution and count rather than copying a generic value.
Does Docker automatically enable Intel Quick Sync?
No. The host driver and device must be available, and the relevant device must be mapped into the container.
Can Frigate Docker record to a NAS?
Yes, but the network share should be mounted reliably on the host and tested for recording copy performance before relying on it.
Should /config and recordings be on the same drive?
They can be, but separating a fast application SSD from bulk recording storage often makes capacity management and replacement easier.
Do I need privileged mode for Frigate?
It depends on the hardware path. Frigate examples may use privileged mode for some setups, but map only the access required by the current documented method.
What should I back up before upgrading Frigate?
Back up configuration and any important exported footage, document device mappings and preserve the compose file so the host can be rebuilt if necessary.
Official references and methodology
Verify current Frigate support before deployment
Cloudzat follows current Frigate Docker installation guidance and separates host, database, shared-memory and recording-storage requirements. The product layer surfaces accepted mini PCs, SSDs and UPS options from this sprint's isolated Amazon catalogue; exact device mappings and driver support must be verified on the chosen Linux platform.
- Frigate - Recording
- Frigate - Installation
- Frigate - Restream
- Frigate - Configuring go2rtc
- Frigate - Troubleshooting Recordings
- Frigate - Camera Setup
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, seller terms, exact configurations, camera firmware and Frigate support can change.