Portainer Templates logo

Portainer Templates

Frigate NVR Frigate NVR

Stack

VideoAI

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.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

dev

Configuration

Command
/bin/sh -c "while sleep 1000; do :; done"
Entrypoint
sudo,/init
Ports
1935:19355000:50005001:50018080:8080
Volumes
/etc/localtime : /etc/localtime/lab/frigate : ./config/config.yml : /portainer/Files/AppData/Config/frigatenvr/config.yml/media/frigate : ./debug/dev/bus/usb : /dev/bus/usb/dev/dri : /dev/dri
Build
[object Object]

mqtt

Configuration

Image
eclipse-mosquitto:1.6
Ports
1883:1883

Image details

Pulls: 677.0M
User: library
Created: Dec 13, 2016
Updated: 1 month ago
Status: active

Standalone Install

Select an install method, to see config/commands for deploying Frigate NVR

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Frigate NVR, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  dev:
    container_name: frigate-dev
    user: vscode
    privileged: true
    shm_size: "256mb"
    build:
      context: .
      dockerfile: docker/Dockerfile.dev
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - .:/lab/frigate:cached
      - /portainer/Files/AppData/Config/frigatenvr/config.yml:/config/config.yml:ro
      - ./debug:/media/frigate
      - /dev/bus/usb:/dev/bus/usb
      - /dev/dri:/dev/dri # for intel hwaccel, needs to be updated for your hardware
    ports:
      - "1935:1935"
      - "5000:5000"
      - "5001:5001"
      - "8080:8080"
    entrypoint: ["sudo", "/init"]
    command: /bin/sh -c "while sleep 1000; do :; done"
  mqtt:
    container_name: mqtt
    image: eclipse-mosquitto:1.6
    ports:
      - "1883:1883"

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/frigatenvr.yml up -d

More install options in our documentation.

Container Documentation

mqtt Documentation

Eclipse Mosquitto is an open source message broker which implements MQTT version 5, 3.1.1 and 3.1

Serve Frigate NVR on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying frigate-nvr.example.com to http://dev:8080

Add this to your Caddyfile

frigate-nvr.example.com {
	reverse_proxy http://dev:8080
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:1935 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :1935
  • Stop the other service, or pick a different host port. In 1935:1935 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, frigatenvr can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8080

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /etc/localtime (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull eclipse-mosquitto:1.6

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.
  • Relative volume paths like ./debug often fail in Portainer because there's no working directory. Swap them for absolute paths.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Frigate NVR is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • dev
  • mqtt runs eclipse-mosquitto:1.6

Ports

A port is the door the app answers on. A mapping like 1935:1935 means it's reachable on port 1935 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8080 in a browser. It opens:

  • 1935:1935
  • 5000:5000
  • 5001:5001
  • 8080:8080, likely the web interface
  • 1883:1883

Volumes

A volume is where Frigate NVR keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /etc/localtime from /etc/localtime on the host
  • /lab/frigate from . on the host
  • /config/config.yml from /portainer/Files/AppData/Config/frigatenvr/config.yml on the host
  • /media/frigate from ./debug on the host
  • /dev/bus/usb from /dev/bus/usb on the host
  • /dev/dri from /dev/dri on the host

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like dev) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Frigate NVR up. Add the template list to Portainer once, then deploying Frigate NVR is a click rather than a wall of config.