dankhostself-host anything

Frigate with Docker Compose

A complete and local NVR designed for Home Assistant with AI object detection. Uses OpenCV and Tensorflow to perform realtime object detection locally for IP cameras. In the project's words: Frigate README on GitHub checked 2026-09-26

Runs on: amd64, arm64 from each image's registry manifest, checked 2026-09-26; a CPU counts only if every image has a build for it. Image by image

Add Frigate to the builder to use your own domain and combine it with other apps in one file.

What Frigate needs

Only figures Frigate's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.

ResourceMinimumRecommended
RAMThe project publishes no figure
CPUThe project publishes no figure
No CPU figure is published. The README says a GPU or AI accelerator is highly recommended: accelerators outperform even the best CPUs at object detection. Source: Frigate README on GitHub checked 2026-09-26
DiskThe project publishes no figure

On top of this, Caddy (the reverse proxy in the file) is a single small container.

Which hardware Frigate has images for

Read from each image's manifest list in its registry (anonymous, read-only) when this page was built. An app counts for a CPU only if every one of its images lists it.

  • x86-64 PC or NAS (linux/amd64): every image has a build.
  • Raspberry Pi 4/5, 64-bit OS (linux/arm64): every image has a build.
  • Raspberry Pi 3 or Zero 2 W, 32-bit OS (linux/arm/v7): no image for frigate. No image for this hardware; the builder leaves the app out.
ServiceImagePlatforms in the manifestDigestRegistryChecked
frigateghcr.io/blakeblackshear/frigate:stableamd64, arm64sha256:9678a83a76e4730ac7d9ea7428370e32ae656d6b312aaad30d6c69f3fef14d35ghcr.io2026-09-26

A manifest says an image exists for a CPU, not how well Frigate runs on it: a build for arm64 or arm/v7 can still be too slow or need more memory than the board has. The RAM and disk Frigate publishes are in the table above and, for a whole set of apps against a Raspberry Pi, on Will it run on my machine?. A tag like latest can move to a new digest after the date checked.

Your hardware

What runs Frigate's object detection changes the compose file and the detector settings. Pick yours: the files below then show the image tag, the devices: lines or GPU reservation, and a config.yml starter with the detectors: block and the video-decoding preset Frigate's docs give for it, each line quoted from those docs. Where the docs give an explicit device list, privileged: true is gone.

Frigate's docs also document MemryX MX3 (whose setup keeps privileged: true), Intel NPUs, AXERA, NVIDIA Jetson, Rockchip and Synaptics boards and Apple Silicon (whose detector runs outside the container). This page does not write those files; take them from the installation page. Source: Frigate docs: Installation (image tags, device lines, Hailo setup) checked 2026-10-09; Frigate docs: Object detectors checked 2026-10-09

The builder on the front page writes the CPU-only file; for any other choice, copy the files from this page.

Every choice's files come below, one after the other; with JavaScript on, the switch shows only the one you pick.

docker-compose.yml

CPU only

This is exactly what the builder writes for Frigate alone on example.org: the official definition with its published ports removed and Caddy added in front. The time zone is Etc/UTC here; the builder uses your browser's.

# docker-compose.yml built at dankhost.com for: Frigate
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Frigate (nvr.example.org) ----
  # Source: https://docs.frigate.video/frigate/installation (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/getting_started (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/tls (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/reverse_proxy (checked 2026-09-26)
  # Source: https://caddyserver.com/docs/caddyfile/directives/reverse_proxy (checked 2026-09-26)
  # Changed: Removed the '8971:8971', '8554:8554', '8555:8555/tcp' and '8555:8555/udp' ports: Caddy reaches frigate:8971, the port the installation page says reverse proxies should use. RTSP and WebRTC are not published; the notes say how to add them.
  #          Written from the installation page's compose generator for a standard x86-64 machine; the folders are ./config and ./storage (the getting-started layout) and TZ is your time zone. The generator's optional FRIGATE_RTSP_PASSWORD is left out: it only matters if your camera settings refer to {FRIGATE_RTSP_PASSWORD}.
  #          Caddy talks HTTPS to port 8971 and accepts Frigate's self-signed certificate with tls_insecure_skip_verify: one of the two ways Frigate's TLS page gives (the other is turning TLS off in Frigate).
  # ELEVATED ACCESS (privileged: true): kept from Frigate's installation page, which says it "may not be necessary for all setups". It gives the container every host device, so a Coral, a GPU at /dev/dri or a Raspberry Pi's /dev/video11 works without a devices: list, and nearly all of root's power on the host. To drop it, delete privileged and add only the devices: lines for your hardware from that page.
  # ELEVATED ACCESS (shm_size: 512mb): shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".
  frigate:
    image: "ghcr.io/blakeblackshear/frigate:stable"
    container_name: "frigate"
    privileged: true
    restart: "unless-stopped"
    stop_grace_period: "30s"
    shm_size: "512mb"
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "./frigate/config:/config"
      - "./frigate/storage:/media/frigate"
      - type: "tmpfs"
        target: "/tmp/cache"
        tmpfs:
          size: 1000000000
    environment:
      TZ: "Etc/UTC"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:

Nothing to add to config.yml: with no detectors: block, Frigate runs its default detector on the CPU. “By default, Frigate will use a single OpenVINO detector running on the CPU.” Frigate docs: Getting started (OpenVINO on an Intel GPU) checked 2026-10-09

With Coral USB

A Google Coral USB Accelerator plugged into the server. For a USB Coral: privileged: true replaced by the USB Coral line of the installation page's example compose (devices: /dev/bus/usb:/dev/bus/usb). Everything else is the CPU-only file, as the builder writes it for Frigate alone on example.org.

# docker-compose.yml built at dankhost.com for: Frigate
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Frigate (nvr.example.org) ----
  # Source: https://docs.frigate.video/frigate/installation (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/getting_started (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/tls (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/reverse_proxy (checked 2026-09-26)
  # Source: https://caddyserver.com/docs/caddyfile/directives/reverse_proxy (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
  # Changed: Removed the '8971:8971', '8554:8554', '8555:8555/tcp' and '8555:8555/udp' ports: Caddy reaches frigate:8971, the port the installation page says reverse proxies should use. RTSP and WebRTC are not published; the notes say how to add them.
  #          Written from the installation page's compose generator for a standard x86-64 machine; the folders are ./config and ./storage (the getting-started layout) and TZ is your time zone. The generator's optional FRIGATE_RTSP_PASSWORD is left out: it only matters if your camera settings refer to {FRIGATE_RTSP_PASSWORD}.
  #          Caddy talks HTTPS to port 8971 and accepts Frigate's self-signed certificate with tls_insecure_skip_verify: one of the two ways Frigate's TLS page gives (the other is turning TLS off in Frigate).
  #          For a USB Coral: privileged: true replaced by the USB Coral line of the installation page's example compose (devices: /dev/bus/usb:/dev/bus/usb).
  # ELEVATED ACCESS (devices: /dev/bus/usb:/dev/bus/usb): in place of privileged: true, the line Frigate's installation page gives for a USB Coral. It passes the host's whole USB bus into the container (every USB device on it, not only the Coral) and no other host device.
  # ELEVATED ACCESS (shm_size: 512mb): shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".
  frigate:
    image: "ghcr.io/blakeblackshear/frigate:stable"
    container_name: "frigate"
    restart: "unless-stopped"
    stop_grace_period: "30s"
    shm_size: "512mb"
    devices:
      - "/dev/bus/usb:/dev/bus/usb"
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "./frigate/config:/config"
      - "./frigate/storage:/media/frigate"
      - type: "tmpfs"
        target: "/tmp/cache"
        tmpfs:
          size: 1000000000
    environment:
      TZ: "Etc/UTC"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:

config.yml starter for Coral USB

The detectors: block as Frigate's docs print them. The docs give no video-decoding preset for this hardware, so none is added.

# config.yml starter for Coral USB, from Frigate's docs. Merge these keys into
# ./frigate/config/config.yml (Frigate writes that file on its first start); your cameras stay as they are.
# Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
detectors:
  coral:
    type: edgetpu
    device: usb

  • ghcr.io/blakeblackshear/frigate:stable: “image: ghcr.io/blakeblackshear/frigate:stable” Frigate docs: Installation (image tags, device lines, Hailo setup) checked 2026-10-09
  • /dev/bus/usb:/dev/bus/usb: “- /dev/bus/usb:/dev/bus/usb # Passes the USB Coral, needs to be modified for other versions” Frigate docs: Installation (image tags, device lines, Hailo setup) checked 2026-10-09
  • No model to download: the Coral detector uses the model inside the image. “A TensorFlow Lite model is provided in the container at /edgetpu_model.tflite and is used by this detector type by default.” Frigate docs: Object detectors checked 2026-10-09
  • The Coral only runs object detection. Video decoding stays on the CPU unless you also pass a GPU (the Intel and AMD choices show its device line and preset). “The Edge TPU detector type runs TensorFlow Lite models utilizing the Google Coral delegate for hardware acceleration.” Frigate docs: Object detectors checked 2026-10-09

With Coral M.2 / PCIe

A Google Coral on an M.2 or Mini PCIe card inside the server. For a PCIe or M.2 Coral: privileged: true replaced by the PCIe Coral line of the installation page's example compose (devices: /dev/apex_0:/dev/apex_0). Everything else is the CPU-only file, as the builder writes it for Frigate alone on example.org.

# docker-compose.yml built at dankhost.com for: Frigate
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Frigate (nvr.example.org) ----
  # Source: https://docs.frigate.video/frigate/installation (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/getting_started (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/tls (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/reverse_proxy (checked 2026-09-26)
  # Source: https://caddyserver.com/docs/caddyfile/directives/reverse_proxy (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
  # Changed: Removed the '8971:8971', '8554:8554', '8555:8555/tcp' and '8555:8555/udp' ports: Caddy reaches frigate:8971, the port the installation page says reverse proxies should use. RTSP and WebRTC are not published; the notes say how to add them.
  #          Written from the installation page's compose generator for a standard x86-64 machine; the folders are ./config and ./storage (the getting-started layout) and TZ is your time zone. The generator's optional FRIGATE_RTSP_PASSWORD is left out: it only matters if your camera settings refer to {FRIGATE_RTSP_PASSWORD}.
  #          Caddy talks HTTPS to port 8971 and accepts Frigate's self-signed certificate with tls_insecure_skip_verify: one of the two ways Frigate's TLS page gives (the other is turning TLS off in Frigate).
  #          For a PCIe or M.2 Coral: privileged: true replaced by the PCIe Coral line of the installation page's example compose (devices: /dev/apex_0:/dev/apex_0).
  # ELEVATED ACCESS (devices: /dev/apex_0:/dev/apex_0): in place of privileged: true, the line Frigate's installation page gives for a PCIe Coral: the one device node the Coral's host driver creates, and no other host device.
  # ELEVATED ACCESS (shm_size: 512mb): shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".
  frigate:
    image: "ghcr.io/blakeblackshear/frigate:stable"
    container_name: "frigate"
    restart: "unless-stopped"
    stop_grace_period: "30s"
    shm_size: "512mb"
    devices:
      - "/dev/apex_0:/dev/apex_0"
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "./frigate/config:/config"
      - "./frigate/storage:/media/frigate"
      - type: "tmpfs"
        target: "/tmp/cache"
        tmpfs:
          size: 1000000000
    environment:
      TZ: "Etc/UTC"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:

config.yml starter for Coral M.2 / PCIe

The detectors: block as Frigate's docs print them. The docs give no video-decoding preset for this hardware, so none is added.

# config.yml starter for Coral M.2 / PCIe, from Frigate's docs. Merge these keys into
# ./frigate/config/config.yml (Frigate writes that file on its first start); your cameras stay as they are.
# Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
detectors:
  coral:
    type: edgetpu
    device: pci

With Intel GPU (OpenVINO)

The integrated graphics of an Intel CPU (or an Intel Arc card), used for both object detection (OpenVINO) and video decoding. For an Intel GPU: privileged: true replaced by the GPU line of the installation page's example compose (devices: /dev/dri/renderD128:/dev/dri/renderD128). Everything else is the CPU-only file, as the builder writes it for Frigate alone on example.org.

# docker-compose.yml built at dankhost.com for: Frigate
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Frigate (nvr.example.org) ----
  # Source: https://docs.frigate.video/frigate/installation (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/getting_started (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/tls (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/reverse_proxy (checked 2026-09-26)
  # Source: https://caddyserver.com/docs/caddyfile/directives/reverse_proxy (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/hardware_acceleration_video (checked 2026-10-09)
  # Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
  # Changed: Removed the '8971:8971', '8554:8554', '8555:8555/tcp' and '8555:8555/udp' ports: Caddy reaches frigate:8971, the port the installation page says reverse proxies should use. RTSP and WebRTC are not published; the notes say how to add them.
  #          Written from the installation page's compose generator for a standard x86-64 machine; the folders are ./config and ./storage (the getting-started layout) and TZ is your time zone. The generator's optional FRIGATE_RTSP_PASSWORD is left out: it only matters if your camera settings refer to {FRIGATE_RTSP_PASSWORD}.
  #          Caddy talks HTTPS to port 8971 and accepts Frigate's self-signed certificate with tls_insecure_skip_verify: one of the two ways Frigate's TLS page gives (the other is turning TLS off in Frigate).
  #          For an Intel GPU: privileged: true replaced by the GPU line of the installation page's example compose (devices: /dev/dri/renderD128:/dev/dri/renderD128).
  # ELEVATED ACCESS (devices: /dev/dri/renderD128:/dev/dri/renderD128): in place of privileged: true, the GPU line from Frigate's installation page, used for decoding and for OpenVINO. Its comment there says it "needs to be updated for your hardware": renderD128 is the first GPU, and ls -l /dev/dri on the host lists one renderD node per GPU.
  # ELEVATED ACCESS (shm_size: 512mb): shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".
  frigate:
    image: "ghcr.io/blakeblackshear/frigate:stable"
    container_name: "frigate"
    restart: "unless-stopped"
    stop_grace_period: "30s"
    shm_size: "512mb"
    devices:
      - "/dev/dri/renderD128:/dev/dri/renderD128"
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "./frigate/config:/config"
      - "./frigate/storage:/media/frigate"
      - type: "tmpfs"
        target: "/tmp/cache"
        tmpfs:
          size: 1000000000
    environment:
      TZ: "Etc/UTC"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:

config.yml starter for Intel GPU (OpenVINO)

The detectors: block and the model: settings and the hwaccel_args preset (preset-vaapi) as Frigate's docs print them.

# config.yml starter for Intel GPU (OpenVINO), from Frigate's docs. Merge these keys into
# ./frigate/config/config.yml (Frigate writes that file on its first start); your cameras stay as they are.
# Source: https://docs.frigate.video/guides/getting_started (checked 2026-10-09)
detectors:
  ov:
    type: openvino
    device: GPU

# We will use the default MobileNet_v2 model from OpenVINO.
model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  path: /openvino-model/ssdlite_mobilenet_v2.xml
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt

# Video decoding. Source: https://docs.frigate.video/configuration/hardware_acceleration_video (checked 2026-10-09)
ffmpeg:
  hwaccel_args: preset-vaapi

With AMD GPU (ROCm)

An AMD graphics card (or AMD integrated graphics) running the ONNX detector through ROCm, plus VAAPI video decoding. For an AMD GPU: the stable-rocm image, the two devices the object detectors page lists for ROCm (/dev/dri and /dev/kfd) in place of privileged: true, and LIBVA_DRIVER_NAME=radeonsi from the hardware acceleration page. Everything else is the CPU-only file, as the builder writes it for Frigate alone on example.org.

# docker-compose.yml built at dankhost.com for: Frigate
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Frigate (nvr.example.org) ----
  # Source: https://docs.frigate.video/frigate/installation (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/getting_started (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/tls (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/reverse_proxy (checked 2026-09-26)
  # Source: https://caddyserver.com/docs/caddyfile/directives/reverse_proxy (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
  # Source: https://docs.frigate.video/configuration/hardware_acceleration_video (checked 2026-10-09)
  # Changed: Removed the '8971:8971', '8554:8554', '8555:8555/tcp' and '8555:8555/udp' ports: Caddy reaches frigate:8971, the port the installation page says reverse proxies should use. RTSP and WebRTC are not published; the notes say how to add them.
  #          Written from the installation page's compose generator for a standard x86-64 machine; the folders are ./config and ./storage (the getting-started layout) and TZ is your time zone. The generator's optional FRIGATE_RTSP_PASSWORD is left out: it only matters if your camera settings refer to {FRIGATE_RTSP_PASSWORD}.
  #          Caddy talks HTTPS to port 8971 and accepts Frigate's self-signed certificate with tls_insecure_skip_verify: one of the two ways Frigate's TLS page gives (the other is turning TLS off in Frigate).
  #          For an AMD GPU: the stable-rocm image, the two devices the object detectors page lists for ROCm (/dev/dri and /dev/kfd) in place of privileged: true, and LIBVA_DRIVER_NAME=radeonsi from the hardware acceleration page.
  # ELEVATED ACCESS (devices: /dev/dri, /dev/kfd): in place of privileged: true, the two devices Frigate's object detectors page says ROCm needs: the GPU nodes under /dev/dri and /dev/kfd, the AMD Kernel Fusion Driver ROCm computes through. No other host device.
  # ELEVATED ACCESS (shm_size: 512mb): shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".
  frigate:
    image: "ghcr.io/blakeblackshear/frigate:stable-rocm"
    container_name: "frigate"
    restart: "unless-stopped"
    stop_grace_period: "30s"
    shm_size: "512mb"
    devices:
      - "/dev/dri"
      - "/dev/kfd"
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "./frigate/config:/config"
      - "./frigate/storage:/media/frigate"
      - type: "tmpfs"
        target: "/tmp/cache"
        tmpfs:
          size: 1000000000
    environment:
      TZ: "Etc/UTC"
      LIBVA_DRIVER_NAME: "radeonsi"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:

config.yml starter for AMD GPU (ROCm)

The detectors: block and the model: settings and the hwaccel_args preset (preset-vaapi) as Frigate's docs print them.

# config.yml starter for AMD GPU (ROCm), from Frigate's docs. Merge these keys into
# ./frigate/config/config.yml (Frigate writes that file on its first start); your cameras stay as they are.
# Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
detectors:
  onnx:
    type: onnx

model:
  model_type: yolo-generic
  width: 320 # <--- should match the imgsize set during model export
  height: 320 # <--- should match the imgsize set during model export
  input_tensor: nchw
  input_dtype: float
  path: /config/model_cache/yolo.onnx # use the filename you generated above
  labelmap_path: /labelmap/coco-80.txt

# Video decoding. Source: https://docs.frigate.video/configuration/hardware_acceleration_video (checked 2026-10-09)
ffmpeg:
  hwaccel_args: preset-vaapi

  • ghcr.io/blakeblackshear/frigate:stable-rocm: “In order to utilize the AMD GPU for object detection use a frigate docker image with -rocm suffix, for example ghcr.io/blakeblackshear/frigate:stable-rocm.” Frigate docs: Object detectors checked 2026-10-09
  • /dev/dri: “ devices: - /dev/dri - /dev/kfd” Frigate docs: Object detectors checked 2026-10-09
  • /dev/kfd: “ devices: - /dev/dri - /dev/kfd” Frigate docs: Object detectors checked 2026-10-09
  • LIBVA_DRIVER_NAME=radeonsi: “You need to change the driver to radeonsi by adding the following environment variable LIBVA_DRIVER_NAME=radeonsi to your docker-compose file” Frigate docs: Hardware acceleration, video decoding checked 2026-10-09
  • preset-vaapi: “ffmpeg: hwaccel_args: preset-vaapi” Frigate docs: Hardware acceleration, video decoding checked 2026-10-09
  • The model file must exist before Frigate starts: export YOLOv9 to ONNX with the docker build command on the object detectors page and save it as ./frigate/config/model_cache/yolo.onnx. “YOLOv9 model can be exported as ONNX using the command below.” Frigate docs: Object detectors checked 2026-10-09
  • Integrated AMD graphics, and some cards, also need the HSA_OVERRIDE_GFX_VERSION environment variable; the object detectors page explains how to find the value. “One has to configure the HSA_OVERRIDE_GFX_VERSION environment variable.” Frigate docs: Object detectors checked 2026-10-09

With NVIDIA GPU

An NVIDIA graphics card on an x86-64 server, running the ONNX detector through TensorRT and decoding video with NVDEC. For an NVIDIA GPU: the stable-tensorrt image and the deploy: GPU reservation of the hardware acceleration page in place of privileged: true. Its device_ids line is left out: Docker allows count or device_ids, not both, and Frigate's comment says device_ids is only needed with several GPUs. Everything else is the CPU-only file, as the builder writes it for Frigate alone on example.org.

# docker-compose.yml built at dankhost.com for: Frigate
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Frigate (nvr.example.org) ----
  # Source: https://docs.frigate.video/frigate/installation (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/getting_started (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/tls (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/reverse_proxy (checked 2026-09-26)
  # Source: https://caddyserver.com/docs/caddyfile/directives/reverse_proxy (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/hardware_acceleration_video (checked 2026-10-09)
  # Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
  # Source: https://docs.docker.com/compose/how-tos/gpu-support/ (checked 2026-10-09)
  # Changed: Removed the '8971:8971', '8554:8554', '8555:8555/tcp' and '8555:8555/udp' ports: Caddy reaches frigate:8971, the port the installation page says reverse proxies should use. RTSP and WebRTC are not published; the notes say how to add them.
  #          Written from the installation page's compose generator for a standard x86-64 machine; the folders are ./config and ./storage (the getting-started layout) and TZ is your time zone. The generator's optional FRIGATE_RTSP_PASSWORD is left out: it only matters if your camera settings refer to {FRIGATE_RTSP_PASSWORD}.
  #          Caddy talks HTTPS to port 8971 and accepts Frigate's self-signed certificate with tls_insecure_skip_verify: one of the two ways Frigate's TLS page gives (the other is turning TLS off in Frigate).
  #          For an NVIDIA GPU: the stable-tensorrt image and the deploy: GPU reservation of the hardware acceleration page in place of privileged: true. Its device_ids line is left out: Docker allows count or device_ids, not both, and Frigate's comment says device_ids is only needed with several GPUs.
  # ELEVATED ACCESS (deploy: one NVIDIA GPU): in place of privileged: true, the GPU reservation from Frigate's hardware acceleration page. Docker hands the container one NVIDIA GPU through the NVIDIA Container Toolkit, which has to be installed on the host first; no other host device.
  # ELEVATED ACCESS (shm_size: 512mb): shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".
  frigate:
    image: "ghcr.io/blakeblackshear/frigate:stable-tensorrt"
    container_name: "frigate"
    restart: "unless-stopped"
    stop_grace_period: "30s"
    shm_size: "512mb"
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "./frigate/config:/config"
      - "./frigate/storage:/media/frigate"
      - type: "tmpfs"
        target: "/tmp/cache"
        tmpfs:
          size: 1000000000
    environment:
      TZ: "Etc/UTC"
    deploy:
      resources:
        reservations:
          devices:
            - driver: "nvidia"
              count: 1
              capabilities:
                - "gpu"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:

config.yml starter for NVIDIA GPU

The detectors: block and the model: settings and the hwaccel_args preset (preset-nvidia) as Frigate's docs print them.

# config.yml starter for NVIDIA GPU, from Frigate's docs. Merge these keys into
# ./frigate/config/config.yml (Frigate writes that file on its first start); your cameras stay as they are.
# Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
detectors:
  onnx:
    type: onnx

model:
  model_type: yolo-generic
  width: 320 # <--- should match the imgsize set during model export
  height: 320 # <--- should match the imgsize set during model export
  input_tensor: nchw
  input_dtype: float
  path: /config/model_cache/yolo.onnx # use the filename you generated above
  labelmap_path: /labelmap/coco-80.txt

# Video decoding. Source: https://docs.frigate.video/configuration/hardware_acceleration_video (checked 2026-10-09)
ffmpeg:
  hwaccel_args: preset-nvidia

With Hailo-8 / 8L

A Hailo-8 or Hailo-8L accelerator, as an M.2 card or a Raspberry Pi HAT. For a Hailo-8 or 8L: privileged: true replaced by the device line of the installation page's Hailo section (devices: /dev/hailo0). Everything else is the CPU-only file, as the builder writes it for Frigate alone on example.org.

# docker-compose.yml built at dankhost.com for: Frigate
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Frigate (nvr.example.org) ----
  # Source: https://docs.frigate.video/frigate/installation (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/getting_started (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/tls (checked 2026-09-26)
  # Source: https://docs.frigate.video/guides/reverse_proxy (checked 2026-09-26)
  # Source: https://caddyserver.com/docs/caddyfile/directives/reverse_proxy (checked 2026-09-26)
  # Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
  # Changed: Removed the '8971:8971', '8554:8554', '8555:8555/tcp' and '8555:8555/udp' ports: Caddy reaches frigate:8971, the port the installation page says reverse proxies should use. RTSP and WebRTC are not published; the notes say how to add them.
  #          Written from the installation page's compose generator for a standard x86-64 machine; the folders are ./config and ./storage (the getting-started layout) and TZ is your time zone. The generator's optional FRIGATE_RTSP_PASSWORD is left out: it only matters if your camera settings refer to {FRIGATE_RTSP_PASSWORD}.
  #          Caddy talks HTTPS to port 8971 and accepts Frigate's self-signed certificate with tls_insecure_skip_verify: one of the two ways Frigate's TLS page gives (the other is turning TLS off in Frigate).
  #          For a Hailo-8 or 8L: privileged: true replaced by the device line of the installation page's Hailo section (devices: /dev/hailo0).
  # ELEVATED ACCESS (devices: /dev/hailo0): in place of privileged: true, the one device line Frigate's installation page gives for a Hailo-8 or 8L; no other host device.
  # ELEVATED ACCESS (shm_size: 512mb): shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".
  frigate:
    image: "ghcr.io/blakeblackshear/frigate:stable"
    container_name: "frigate"
    restart: "unless-stopped"
    stop_grace_period: "30s"
    shm_size: "512mb"
    devices:
      - "/dev/hailo0"
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "./frigate/config:/config"
      - "./frigate/storage:/media/frigate"
      - type: "tmpfs"
        target: "/tmp/cache"
        tmpfs:
          size: 1000000000
    environment:
      TZ: "Etc/UTC"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:

config.yml starter for Hailo-8 / 8L

The detectors: block and the model: settings as Frigate's docs print them. The docs give no video-decoding preset for this hardware, so none is added.

# config.yml starter for Hailo-8 / 8L, from Frigate's docs. Merge these keys into
# ./frigate/config/config.yml (Frigate writes that file on its first start); your cameras stay as they are.
# Source: https://docs.frigate.video/configuration/object_detectors (checked 2026-10-09)
detectors:
  hailo:
    type: hailo8l
    device: PCIe

model:
  width: 320
  height: 320
  input_tensor: nhwc
  input_pixel_format: rgb
  input_dtype: int
  model_type: yolo-generic
  labelmap_path: /labelmap/coco-80.txt

Caddyfile save as caddy/Caddyfile

Caddy gets and renews the HTTPS certificate for nvr.example.org by itself once the DNS record points at your server and ports 80 and 443 reach it.

# Caddyfile built at dankhost.com. Save it as ./caddy/Caddyfile next to docker-compose.yml.
# Caddy gets and renews a Let's Encrypt certificate for each name below by itself,
# once the DNS records point at this server and ports 80 and 443 reach it.

# Frigate
nvr.example.org {
	reverse_proxy frigate:8971 {
		transport http {
			tls_insecure_skip_verify
		}
	}
}

Already running nginx, Nginx Proxy Manager, Caddy or Traefik? The reverse-proxy settings Frigate needs, for all four, each cited to Frigate's own docs.

.env

Frigate needs no secret here; the builder adds nothing you have to fill in by hand.

# .env for Frigate, from dankhost.com/app/frigate/. Nothing here is secret.
# Keep this file private (chmod 600).
# None of the chosen apps needs a variable here.

What Frigate needs beyond the proxy

Frigate asks for more than an ordinary container. The compose file keeps what the project documents and labels each item with an # ELEVATED ACCESS comment; /check/ flags them too, as it would in any file.

  • privileged: true: kept from Frigate's installation page, which says it "may not be necessary for all setups". It gives the container every host device, so a Coral, a GPU at /dev/dri or a Raspberry Pi's /dev/video11 works without a devices: list, and nearly all of root's power on the host. To drop it, delete privileged and add only the devices: lines for your hardware from that page.
  • shm_size: 512mb: shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".

With Coral USB, the compose file labels each of these with an # ELEVATED ACCESS comment. /check/ raises no finding on this file: without privileged, nothing in it is on /check/'s list.

  • devices: /dev/bus/usb:/dev/bus/usb: in place of privileged: true, the line Frigate's installation page gives for a USB Coral. It passes the host's whole USB bus into the container (every USB device on it, not only the Coral) and no other host device.
  • shm_size: 512mb: shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".

With Coral M.2 / PCIe, the compose file labels each of these with an # ELEVATED ACCESS comment. /check/ raises no finding on this file: without privileged, nothing in it is on /check/'s list.

  • devices: /dev/apex_0:/dev/apex_0: in place of privileged: true, the line Frigate's installation page gives for a PCIe Coral: the one device node the Coral's host driver creates, and no other host device.
  • shm_size: 512mb: shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".

With Intel GPU (OpenVINO), the compose file labels each of these with an # ELEVATED ACCESS comment. /check/ raises no finding on this file: without privileged, nothing in it is on /check/'s list.

  • devices: /dev/dri/renderD128:/dev/dri/renderD128: in place of privileged: true, the GPU line from Frigate's installation page, used for decoding and for OpenVINO. Its comment there says it "needs to be updated for your hardware": renderD128 is the first GPU, and ls -l /dev/dri on the host lists one renderD node per GPU.
  • shm_size: 512mb: shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".

With AMD GPU (ROCm), the compose file labels each of these with an # ELEVATED ACCESS comment. /check/ raises no finding on this file: without privileged, nothing in it is on /check/'s list.

  • devices: /dev/dri, /dev/kfd: in place of privileged: true, the two devices Frigate's object detectors page says ROCm needs: the GPU nodes under /dev/dri and /dev/kfd, the AMD Kernel Fusion Driver ROCm computes through. No other host device.
  • shm_size: 512mb: shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".

With NVIDIA GPU, the compose file labels each of these with an # ELEVATED ACCESS comment. /check/ raises no finding on this file: without privileged, nothing in it is on /check/'s list.

  • deploy: one NVIDIA GPU: in place of privileged: true, the GPU reservation from Frigate's hardware acceleration page. Docker hands the container one NVIDIA GPU through the NVIDIA Container Toolkit, which has to be installed on the host first; no other host device.
  • shm_size: 512mb: shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".

With Hailo-8 / 8L, the compose file labels each of these with an # ELEVATED ACCESS comment. /check/ raises no finding on this file: without privileged, nothing in it is on /check/'s list.

  • devices: /dev/hailo0: in place of privileged: true, the one device line Frigate's installation page gives for a Hailo-8 or 8L; no other host device.
  • shm_size: 512mb: shared memory for decoded frames, the installation page's value. Its formula per camera is (width x height x 1.5 x 20 + 270480) / 1048576 MB at the detect resolution, about 27MB for 1280x720, plus up to 40MB for logs; raise it if Frigate exits with "Bus error".

Changes from the official file

Besides prefixing every service, container, volume, folder and variable with frigate (so any set of apps can share one file), these are all the differences from what the project documents:

  • Removed the '8971:8971', '8554:8554', '8555:8555/tcp' and '8555:8555/udp' ports: Caddy reaches frigate:8971, the port the installation page says reverse proxies should use. RTSP and WebRTC are not published; the notes say how to add them.
  • Written from the installation page's compose generator for a standard x86-64 machine; the folders are ./config and ./storage (the getting-started layout) and TZ is your time zone. The generator's optional FRIGATE_RTSP_PASSWORD is left out: it only matters if your camera settings refer to {FRIGATE_RTSP_PASSWORD}.
  • Caddy talks HTTPS to port 8971 and accepts Frigate's self-signed certificate with tls_insecure_skip_verify: one of the two ways Frigate's TLS page gives (the other is turning TLS off in Frigate).

Notes for Frigate behind the proxy

  • Log in at https://nvr.example.org as admin with the password Frigate prints on its first start: docker compose logs frigate | grep -i password. Change it under Settings > Users.
  • Frigate creates its config file on the first start; add your cameras in the UI or in ./frigate/config/config.yml.
  • RTSP restreaming (8554) and WebRTC (8555) are not published. To use them from devices on your network, add under the frigate service:
    ports:
    - "8554:8554"
    - "8555:8555/tcp"
    - "8555:8555/udp"
    The installation page says these RTSP streams are unauthenticated by default (the go2rtc section can add authentication), so never forward 8554 from your router.
  • Caddy talks HTTPS to port 8971, which serves Frigate's own self-signed certificate by default, and accepts it with tls_insecure_skip_verify; Caddy's docs warn that option makes that hop open to a man in the middle, and here the hop is the Docker network inside this server. Visitors still get Caddy's Let's Encrypt certificate. To avoid it, turn TLS off in Frigate (Settings > System > TLS) and delete the transport block.
  • Without a Coral, GPU or other detector, object detection runs on the CPU; the README says a GPU or AI accelerator is highly recommended.

How to run it

  1. At your DNS provider, add an A record named nvr on your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it.
  2. Save the three files in one folder: docker-compose.yml and .env side by side, the Caddyfile at ./caddy/Caddyfile. Replace example.org with your domain in the Caddyfile, the compose file and the .env, or let the builder do it.
  3. Nothing in .env needs filling in; chmod 600 .env all the same.
  4. Start it:
    docker compose up -d
    docker compose logs -f caddy   # watch the certificate arrive
  5. Open the new address (nvr. plus your domain) in a browser and follow the notes above.

Back it up

The installation page: /config holds the Frigate config file and its SQLite database; /media/frigate holds recordings, snapshots (clips) and exports; /tmp/cache is a tmpfs in memory.

Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, what to copy with which container stopped, and a restore check. Pick more apps in the builder and it covers them all in one file.

# BACKUP.md built at dankhost.com for: Frigate

What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.

The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.

Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.

## Before you start

    BACKUP=/mnt/backup/selfhost   # change this: a disk or machine other than this server's system disk
    mkdir -p "$BACKUP"

## Every time: the three stack files

    tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy

.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.

## Caddy (the reverse proxy)

Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.

- caddy-data (named volume, /data in caddy)
  BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
  SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
  IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.

Copy (Caddy keeps serving while you copy):

    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data

Restore check:

    tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"

Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)

## Frigate

The installation page: /config holds the Frigate config file and its SQLite database; /media/frigate holds recordings, snapshots (clips) and exports; /tmp/cache is a tmpfs in memory.

What this compose mounts:
- ./frigate/config (/config in frigate)
  BACK UP: config.yml and the SQLite database (events, users).
- ./frigate/storage (/media/frigate in frigate)
  OPTIONAL: recordings, snapshots and exports. Often hundreds of gigabytes; Frigate deletes old recordings by its retention settings.

1. Stop frigate. Stopping it keeps the SQLite database from changing mid-copy. Nothing is recorded until it is back.

    docker compose stop frigate

2. Copy while frigate is stopped:

    tar czf "$BACKUP/frigate-config.tar.gz" ./frigate/config

3. Start it again:

    docker compose start frigate

Restore check:

    tar tzf "$BACKUP/frigate-config.tar.gz" > /dev/null && echo OK

Put a copy back (with frigate stopped):

    tar xzf "$BACKUP/frigate-config.tar.gz"   # recreates ./frigate/config; move the old folder aside first

Stop it, put ./frigate/config (and ./frigate/storage if you kept it) back, start it.

Sources:
- Frigate docs: Installation (storage, ports, shm size, Docker Compose generator and example): https://docs.frigate.video/frigate/installation (checked 2026-09-26)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-26)

Update it

What docker compose pull does depends only on how each image line in the compose file above is tagged. For Frigate as this page writes it:

ServiceImageHow it is pinnedWhat docker compose pull does
caddycaddy:2Major version only (tag 2)Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit.
frigateghcr.io/blakeblackshear/frigate:stableNot pinned: moving tag stableMoves to the newest image published as stable, which can be a new major version.

What Frigate's docs say about updating

Frigate's Updating page: stop Frigate, back up /config (config.yml and frigate.db, its SQLite database), read the release notes for breaking changes, then pull and start the new image and check the container log that it started cleanly.

  • With the stable tag used here you do not edit the tag: Frigate says stable always points to the newest stable release after a pull. To choose the version yourself, write it in the tag (their example is 0.18.0).

Source: Frigate docs: Updating checked 2026-09-30

The steps

  1. Back up first, as in Back it up above. An update can migrate Frigate's data on its first start; the copy is the way back.
  2. Download the new images. Running containers are not touched yet:
    docker compose pull
  3. Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
    docker compose up -d
  4. Watch Frigate start (Ctrl+C stops following the log, not the app):
    docker compose logs -f frigate
  5. Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:
    docker image prune

Docker's reference for these commands: Docker docs: docker compose pull checked 2026-09-30; Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30; Docker docs: docker image prune checked 2026-09-30

Locked out? Reset the admin password

Frigate can reset its admin password itself: one setting makes it pick a new one at the next start and print it in its log.

  1. Add this to ./frigate/config/config.yml (merge it into the auth: block if you have one): Source: Frigate docs: Authentication (Onboarding, Resetting admin password) read 2026-10-03
    auth:
      reset_admin_password: true
  2. Restart Frigate. Source: Frigate docs: Authentication (Onboarding, Resetting admin password) read 2026-10-03; Docker docs: docker compose restart read 2026-10-03
    docker compose restart frigate
  3. Read the new password in the log, log in as admin and set your own under Settings > Users. The docs do not say whether the setting turns itself off, so check config.yml afterwards and remove the line if it is still there. Source: Frigate docs: Authentication (Onboarding, Resetting admin password) read 2026-10-03; Docker docs: docker compose logs read 2026-10-03
    docker compose logs frigate

Run the commands in the folder that holds docker-compose.yml.

Sources

Every page below was fetched on the date shown.

Add Frigate to the builder All one hundred apps

Made with AI tools. · Privacy