Frigate NVR on Proxmox vs Docker: TPU & GPU Passthrough Guide

Frigate proxmox vs docker is not a codec debate—it is a question of how many virtualization layers sit between your Coral TPU, Intel iGPU, and the Frigate container. As of 9 June 2026, bare-metal Docker on Debian or Ubuntu gives the thinnest path to map /dev/dri/renderD128 and a Google Coral USB stick with one Compose file. Proxmox VE 8.4+ adds a hypervisor so you can snapshot Frigate, colocate Home Assistant, and survive kernel bumps—but you must bind-mount GPU nodes into a privileged LXC or pass USB through a VM, or acceleration silently falls back to CPU decode and software detection.

Quick answer: Should Frigate run on Proxmox or Docker for Coral TPU and GPU passthrough?

Run Frigate in Docker on bare metal when the box is NVR-only—direct /dev/dri and USB mapping is simplest. Use Proxmox when you need snapshots and multiple workloads on one Intel host; deploy Frigate inside a privileged LXC with renderD128 and /dev/bus/usb bind-mounted, then run the same Docker Compose stack inside the LXC.

Source: Frigate hardware acceleration

---

Executive summary

Privacy-conscious builders comparing Frigate NVR on Proxmox vs Docker usually already own an Intel N100/N305 mini-PC or a Ugreen NASync DXP and hit the same wall: ffmpeg pegs four cores while /dev/dri and the Coral USB sit unused. Frigate’s documentation (accessed 9 June 2026) treats video decode (QuickSync/VAAPI) and object detection (Coral, Hailo, OpenVINO) as separate layers¹²—your deployment choice only changes how those devices reach the container, not whether you need both at six-plus 1080p cameras.

We compiled the passthrough complexity matrix below by cross-walking Proxmox LXC device docs, Frigate Docker install guidance, and twelve r/HomeAssistant and Frigate GitHub threads dated January–June 2026 that mention Coral or QSV failures after hypervisor updates³⁴⁵.

Verdict: Marcus (Beelink EQ13, six Reolink PoE cams, no other homelab services) should run Docker on Debian 12—one evening, no LXC config. Priya (same hardware plus Home Assistant OS in a VM and Pi-hole LXC) should keep Proxmox and run Frigate in privileged LXC 201 with GPU and USB bind-mounts; the snapshot before Proxmox 8.4→8.5 kernel updates is worth the extra config file.

---

Methodology: how the passthrough matrix was built

1. Layer count — counted hypervisor + container engine + Frigate container from host metal to Frigate process.
2. QSV path — verified against Frigate Intel preset table (preset-intel-qsv-h264 / h265, gen12 iHD driver)¹.
3. Coral USB path — mapped to Proxmox lxc.mount.entry for /dev/bus/usb vs Docker devices: stanza⁴⁵.
4. Rollback — Proxmox snapshot vs Docker volume backup only.
5. Editorial friction score — 1 (trivial) to 5 (frequent forum breakage); aggregated from community reports through June 2026.

Where I’m less sure — exact cgroup rules on Proxmox 9 pre-release builds; validate vainfo after every point release. Anecdotally, USB Coral passthrough survives minor Proxmox updates more often than PCIe Coral M.2 without VM passthrough.

---

Original research: Frigate deployment × hardware passthrough matrix (June 2026)

Deployment	Hypervisor layers	QSV (/dev/dri) path	Coral USB	Coral PCIe M.2	Snapshot rollback	Friction score /5	Best for
Docker on bare Debian/Ubuntu	0	Direct devices: map	Direct devices:	Direct if slot on host	Volume backup only	1	Dedicated NVR mini-PC
Docker on Proxmox host (no LXC)	1	Host /dev/dri → compose	Host USB → compose	Native PCIe on host	VM disk backup	2	Single-app Proxmox install
Proxmox privileged LXC + Docker	2	lxc.mount.entry renderD128	lxc.mount.entry usb bus	Not inside LXC (use host/VM)	pct snapshot	3	HA + Frigate colocation
Proxmox VM + Docker	2	USB/GPU passthrough to VM	USB filter to VM	PCIe passthrough possible	qm snapshot	4	Isolation or PCIe Coral
Home Assistant OS add-on	1–2	HA device passthrough UI	HA USB attach	Limited	HA backup	2	HA-centric users
UGOS Docker (NAS)	0–1	App Center compose	USB map	Rare on NAS	Factory reset	2–3	NASync buyers keeping stock OS

Stat: Frigate documents ~10 ms inference on Coral MobileDet and ~7 ms on Hailo-8 YOLOv6n—decode must be offloaded separately via QuickSync or CPU ffmpeg collapses under six 1080p streams.

Dataset (JSON-LD)

---

Two hardware layers Frigate always needs at scale

Intel Quick Sync Video (QSV) offloads H.264/H.265 decode in ffmpeg. A Google Coral TPU (or Hailo-8) runs object-detection inference on motion crops. Confusing the two is the dominant failure mode in frigate proxmox vs docker threads: users buy a Coral, enable detectors.coral, and wonder why CPU stays at 80% because no /dev/dri map exists for decode¹².

Layer	Hardware	Frigate config	Typical symptom if missing
Decode	Intel iGPU via /dev/dri	hwaccel_args: preset-intel-qsv-h264	ffmpeg 70%+ CPU per stream
Detect	Coral USB / Hailo M.2	detectors.coral.type: edgetpu	High CPU on detect fps; event lag

Cross-read configure Intel QuickSync for preset tables and Coral vs Hailo benchmarks before buying a second accelerator.

---

Steel-man: why bare-metal Docker is the rational default

The strongest case against Proxmox for Frigate is device path simplicity:

On Debian 12 or Ubuntu 24.04 LTS, you install intel-media-va-driver-non-free, plug in a Coral USB Accelerator (~$60 street, Amazon snapshot 9 June 2026), and deploy the official ghcr.io/blakeblackshear/frigate:stable image with two devices: lines. No lxc.cgroup2.devices.allow, no VM USB filters, no SeaBIOS vs OVMF foot-guns. When QSV breaks after a kernel update, you debug one /dev/dri/renderD128 path—not host plus LXC plus Docker. For a Beelink EQ13 ($169–199 barebone, June 2026 pricing) dedicated to cameras, that is an afternoon with rollback = restore Compose from git, which matches how most Frigate documentation examples are written⁵.

Rebuttal: Proxmox earns its layer when the same N100 also runs Home Assistant, AdGuard, and restic backups. A pct snapshot before apt upgrade on the Frigate LXC has saved countless /dev/dri regressions in community reports—bare Docker offers no equally fast rollback for the whole stack. If you already run Proxmox for Home Assistant, adding Frigate LXC is consistent; wiping Proxmox to “simplify” Frigate often increases total homelab risk when other VMs move back to the same metal anyway.

---

Path A — Docker on bare metal (recommended for NVR-only hosts)

Working example: Marcus, Beelink EQ13, six 1080p cameras

Profile: Marcus runs Debian 12 on a Beelink EQ13 (Intel N100, 16 GB RAM). Six Annke I91DN cameras on VLAN 40 with no WAN. He wants local person alerts without cloud retention.

Steps (verified against Frigate 0.15 Docker docs, 9 June 2026):

1. Host drivers — apt install intel-media-va-driver-non-free; reboot.
2. Verify GPU — vainfo --display drm --device /dev/dri/renderD128 lists H264/H265.
3. Compose — map GPU and Coral USB:

services:
  frigate:
    image: ghcr.io/blakeblackshear/frigate:stable
    privileged: true
    shm_size: "256mb"
    restart: unless-stopped
    environment:
      LIBVA_DRIVER_NAME: iHD
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/bus/usb:/dev/bus/usb
    volumes:
      - /opt/frigate/config:/config
      - /mnt/nvr/frigate:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000"
      - "8554:8554"
      - "8555:8555/tcp"
      - "8555:8555/udp"

4. config.yml — QSV decode + Coral detect:

detectors:
  coral:
    type: edgetpu
    device: usb

ffmpeg:
  hwaccel_args: preset-intel-qsv-h264

cameras:
  front_yard:
    ffmpeg:
      inputs:
        - path: rtsp://192.168.40.101/sub
          roles: [detect]
        - path: rtsp://192.168.40.101/main
          roles: [record]
    detect:
      width: 1280
      height: 720
      fps: 5

5. Validate — docker exec frigate vainfo and Frigate System → FFmpeg show hardware acceleration; inference stays 9–11 ms on Coral per Frigate’s published table².

Marcus’s taken position: stay on bare Docker until he adds a second service that needs VM isolation—not before.

---

Path B — Proxmox privileged LXC + Docker (recommended for homelabs)

Working example: Priya, Intel N305, Frigate + Home Assistant

Profile: Priya runs Proxmox VE 8.4 on a Beelink SER5 Max (N305, 32 GB RAM). Home Assistant OS lives in VM 100; Pi-hole in LXC 105; Frigate in privileged LXC 201 with Docker inside.

Host prep:

ls -l /dev/dri/
# note renderD128 major:minor — often 226:128

Edit /etc/pve/lxc/201.conf:

lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file
lxc.mount.entry: /dev/bus/usb dev/bus/usb none bind,optional,create=dir

Restart LXC: pct stop 201 && pct start 201. Inside LXC, install Docker and reuse the same Compose as Marcus. Recordings bind-mount to a ZFS dataset on HDDs (mp0: /tank/nvr,mp=/mnt/nvr), not the Proxmox OS SSD⁴.

Snapshot discipline: pct snapshot 201 pre-pve84-kernel before every Proxmox point upgrade. Where I’m less sure — unprivileged LXC with id-mapped GPUs on Proxmox 8.4; most Frigate homelabs still use privileged for fewer moving parts.

Proxmox LXC + Docker — pros

• Fast rollback when /dev/dri breaks after kernel bumps.
• Colocate Home Assistant without Frigate consuming HA RAM.
• Standard community scripts (e.g. RiceMunk frigate-proxmox patterns) target this layout⁶.

Proxmox LXC + Docker — cons

• Three layers to debug (host → LXC → Docker).
• PCIe Coral M.2 generally requires VM passthrough or host Docker instead.
• USB passthrough can reorder after host reboot—confirm lsusb inside LXC.

Bare Docker — pros

• Shortest device path; matches upstream Frigate examples.
• Lowest idle overhead on N100 when no other VMs run.
• Simplest mental model for VLAN-only NVR appliances.

Bare Docker — cons

• No built-in snapshot; rely on Compose in git + config backups.
• Second app on same box pushes you toward Proxmox anyway.
• You manage host patching without Proxmox GUI orchestration.

---

Path C — Proxmox VM (PCIe Coral or hard isolation)

Choose a VM when you run a PCIe Coral M.2 or Hailo-8 card that cannot route through LXC bind-mounts, or when compliance-style kernel isolation matters. Pass the USB controller or GPU via Proxmox Hardware → Add → USB Device or PCIe passthrough, install Linux inside the VM, then Docker—same Compose as Path A. Expect higher RAM overhead (~4 GB for VM + Docker) and CPU cost for USB virtualization compared to LXC.

I haven’t tested every N100 board’s IOMMU grouping for single-function GPU passthrough; anecdotally, LXC bind-mount remains the default on homelab Intel iGPUs through June 2026.

---

Side-by-side: Proxmox vs Docker for Frigate acceleration

Criterion	Docker on bare metal	Proxmox LXC + Docker	Proxmox VM + Docker
Setup time (first QSV + Coral)	2–4 hours	4–8 hours	6–12 hours
QSV passthrough	devices: /dev/dri/renderD128	lxc.mount.entry + cgroup allow	GPU passthrough or emulated
Coral USB	devices: /dev/bus/usb	USB bus bind-mount	USB device filter to VM
Rollback on bad kernel	Manual restore	pct snapshot	qm snapshot
Colocate HA + Pi-hole	Docker Compose only	Native Proxmox VMs/LXC	Native
Privacy (local footage)	Full local	Full local	Full local
Idle power (N100 est.)	~8–12 W	~10–15 W	~12–18 W

---

Troubleshooting: acceleration silent failures

Symptom	Likely cause	Fix
CPU 70%+, GPU idle	No /dev/dri in container	Add device map; check LXC mount.entry
vainfo fails in container	Driver on host only	Install intel-media-va-driver-non-free on host/LXC
Coral not detected	USB not passed to LXC/VM	Bind /dev/bus/usb; check lsusb inside stack
QSV enabled, ffmpeg errors	H.265 stream with H.264 preset	Per-input preset-intel-qsv-h265
Worked until Proxmox update	LXC config wiped	Re-apply 201.conf lines; snapshot restore
Detect lag, low CPU	Coral missing	Add detectors.coral; QSV does not detect objects

Checklist

• ✓ Install intel-media-va-driver-non-free on the Docker host (or LXC host layer).
• ✓ Set LIBVA_DRIVER_NAME=iHD on Alder Lake-N (N100/N305).
• ✓ Map /dev/dri/renderD128 before inserting Coral USB.
• ✓ Use 720p substream for detect; reserve main stream for record.
• ✓ docker exec frigate vainfo — must list H264/H265 decode.
• ✓ pct snapshot or git-track Compose before Proxmox kernel updates.
• ✓ Block camera VLAN WAN egress on either architecture.

---

Verdict

For frigate proxmox vs docker, the decision is workload colocation—not detection quality. Docker on bare metal is the right call for a dedicated NVR mini-PC where Marcus-style simplicity beats snapshot luxury. Proxmox with a privileged Frigate LXC is the right call when Priya already virtualizes Home Assistant and wants pct snapshot insurance before Intel media driver churn.

Do not deploy Frigate on Proxmox without planning /dev/dri and Coral paths in the same checklist you use for VLAN camera isolation. Pick one architecture, validate vainfo and Coral inference ms, then tune motion masks—swapping Proxmox for Docker rarely fixes a mis-mapped GPU.

---

FAQ

Frequently Asked Questions

Is Proxmox or Docker better for Frigate NVR?

Bare-metal Docker is simpler for a single Frigate host with direct /dev/dri and USB access. Proxmox wins when you colocate Home Assistant, Pi-hole, or backup jobs on the same Intel mini-PC and want snapshot rollback before kernel bumps.

Can Frigate use Intel QuickSync inside a Proxmox LXC?

Yes, in a privileged LXC with renderD128 bind-mounted from the host and intel-media-va-driver-non-free installed. Unprivileged LXC without device cgroup rules typically fails vainfo inside the container.

Does a Coral TPU work through Proxmox passthrough?

Yes—bind-mount /dev/bus/usb into the LXC or pass the USB controller to a VM. PCIe Coral M.2 cards need either host Docker, a VM with PCIe passthrough, or running Frigate on the Proxmox host itself.

Why is Frigate CPU still at 100% with QuickSync enabled?

Usually /dev/dri is missing from the container, LIBVA_DRIVER_NAME is wrong for Alder Lake-N (use iHD), or detect is pointed at a 4K H.265 main stream instead of a 720p substream.

Should I run Frigate in a Proxmox VM instead of LXC?

Choose a VM only when you need kernel isolation or PCIe Coral passthrough. LXC plus Docker is the community default for Intel N100 homelabs because QSV bind-mount is well documented and overhead is lower.

Does Docker on bare metal beat Proxmox for privacy?

Both keep footage local. Privacy difference is operational—fewer daemons on bare Docker, more isolation options on Proxmox. Block camera WAN egress on either stack.

---

Primary Sources

Index	Title / description	URL
1	Frigate — Video decoding (Intel QSV presets)	https://docs.frigate.video/configuration/hardware_acceleration_video/
2	Frigate — Recommended hardware (Coral, Hailo inference)	https://docs.frigate.video/frigate/hardware
3	Frigate — Installation (Docker)	https://docs.frigate.video/frigate/installation
4	Proxmox VE documentation — LXC container configuration	https://pve.proxmox.com/wiki/Linux_Container
5	Google Coral — USB Accelerator product page	https://coral.ai/products/accelerator/
6	RiceMunk/frigate-proxmox-script (community LXC pattern)	https://github.com/RiceMunk/frigate-proxmox-script

Footnotes

1. Frigate video decoding documentation, accessed 9 June 2026 ↩ ↩² ↩³

2. Frigate recommended hardware — detector inference table, accessed 9 June 2026 ↩ ↩² ↩³

3. r/homeassistant Frigate Proxmox threads, sampled January–June 2026 ↩

4. Proxmox VE LXC wiki — device bind mounts ↩ ↩² ↩³

5. Frigate Docker installation guide, accessed 9 June 2026 ↩ ↩² ↩³

6. RiceMunk/frigate-proxmox-script repository, accessed 9 June 2026 ↩

Related guides

• Proxmox vs Docker vs Bare Metal for Home Assistant
• Build a Local NVR on Ugreen NASync with Frigate
• Configure Intel QuickSync for Frigate on Ugreen NASync
• Local NVR Hardware: Coral TPU vs QuickSync vs Hailo-8