Seerr with Docker Compose

What Seerr needs

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

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

Which hardware Seerr 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 seerr. No image for this hardware; the builder leaves the app out.

A manifest says an image exists for a CPU, not how well Seerr 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 Seerr 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.

docker-compose.yml

This is exactly what the builder writes for Seerr 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: Seerr
# 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"

  # ---- Seerr (requests.example.org) ----
  # Source: https://docs.seerr.dev/getting-started/docker (checked 2026-09-30)
  # Source: https://docs.seerr.dev/extending-seerr/reverse-proxy (checked 2026-09-30)
  # Source: https://docs.seerr.dev/using-seerr/settings/network (checked 2026-09-30)
  # Source: https://docs.seerr.dev/migration-guide (checked 2026-09-30)
  # Changed: Removed the documented '5055:5055' port; Caddy reaches seerr:5055 on the proxy network, on its own subdomain: the reverse-proxy page says base URLs cannot be configured, so only subdomains are supported.
  #          The folder /path/to/appdata/config is ./config next to this file. TZ is your time zone instead of the example's Asia/Tashkent.
  seerr:
    image: "ghcr.io/seerr-team/seerr:latest"
    container_name: "seerr"
    init: true
    environment:
      LOG_LEVEL: "debug"
      TZ: "Etc/UTC"
      PORT: "5055"
    volumes:
      - "./seerr/config:/app/config"
    healthcheck:
      test: "wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/settings/public || exit 1"
      start_period: "20s"
      timeout: "3s"
      interval: "15s"
      retries: 3
    security_opt:
      - "no-new-privileges"
    cap_drop:
      - "ALL"
    restart: "unless-stopped"
    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:

Caddyfile save as caddy/Caddyfile

Caddy gets and renews the HTTPS certificate for requests.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.

# Seerr
requests.example.org {
	reverse_proxy seerr:5055
}

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

.env

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

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

Changes from the official file

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

• Removed the documented '5055:5055' port; Caddy reaches seerr:5055 on the proxy network, on its own subdomain: the reverse-proxy page says base URLs cannot be configured, so only subdomains are supported.
• The folder /path/to/appdata/config is ./config next to this file. TZ is your time zone instead of the example's Asia/Tashkent.

Notes for Seerr behind the proxy

• Before the first start: mkdir -p ./seerr/config && sudo chown -R 1000:1000 ./seerr/config. The docs: the container runs as the node user (UID 1000), and without it the settings are not saved.
• Open https://requests.example.org and the setup wizard connects Seerr to your Jellyfin, Plex or Emby server and to Sonarr and Radarr. Then turn on Settings > Network > Enable Proxy Support, so Seerr records each visitor's address instead of the proxy's (it is off by default).
• Coming from Jellyseerr or Overseerr: back up the old config folder, point this service at it and start it; the migration guide says the move to Seerr runs by itself on first start.
• The docs' compose uses the image tag 'latest' ("Always points to the most recent stable release") and LOG_LEVEL=debug; set info if the logs are too chatty.

Back it up

Seerr publishes what to back up: settings.json and the SQLite database db/db.sqlite3, both in the config folder. Without filesystem snapshots, its page says to stop Seerr and back up the config folder.

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: Seerr

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)

## Seerr

Seerr publishes what to back up: settings.json and the SQLite database db/db.sqlite3, both in the config folder. Without filesystem snapshots, its page says to stop Seerr and back up the config folder.

What this compose mounts:
- ./seerr/config (/app/config in seerr)
  BACK UP: settings.json (every Settings panel choice and integration), db/db.sqlite3 (users, requests, blocklist), plus cache and logs, which are optional.

1. Stop seerr. The Backups page: "you need to stop the Seerr application and back up the config folder" unless you use filesystem snapshots.

    docker compose stop seerr

2. Copy while seerr is stopped:

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

3. Start it again:

    docker compose start seerr

Restore check:

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

Put a copy back (with seerr stopped):

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

Put ./seerr/config back (db/db.sqlite3 and settings.json at least), owned by UID 1000, and run docker compose up -d.

Sources:
- Seerr docs: Backups (settings.json and db/db.sqlite3 in the config folder): https://docs.seerr.dev/using-seerr/backups (checked 2026-09-30)

Sources

Every page below was fetched on the date shown.

• Seerr README on GitHub checked 2026-09-30 (what it does)
• Seerr docs: Docker (compose.yaml, tags, config folder owned by UID 1000) checked 2026-09-30 (compose definition and proxy settings)
• Seerr docs: Reverse Proxy (subdomain only; nginx example) checked 2026-09-30 (compose definition and proxy settings)
• Seerr docs: Network settings (Enable Proxy Support) checked 2026-09-30 (compose definition and proxy settings)
• Seerr docs: Migration guide (from Overseerr or Jellyseerr; node user UID 1000; init: true) checked 2026-09-30 (compose definition and proxy settings)
• Caddy docs: Keep Caddy running (Docker Compose section) checked 2026-09-23 (Caddy)
• Vaultwarden wiki: Caddy with HTTP challenge (uses the caddy:2 image) checked 2026-09-23 (Caddy)
• Seerr docs: Backups (settings.json and db/db.sqlite3 in the config folder) checked 2026-09-30 (backup plan)
• Caddy docs: Conventions, Data directory checked 2026-09-24 (backup plan)
• Docker docs: Volumes, Back up, restore, or migrate data volumes checked 2026-09-24 (backup plan)

Add Seerr to the builder All sixty apps