Self-host Seerr with Levelrail

A media request manager for Jellyfin, Plex and Emby with Sonarr and Radarr hand-off, the merged successor of Overseerr and Jellyseerr. MIT licensed. On first open, sign in with your media server account to become the admin.

  • Authorseerr-team
  • LicenceMIT
  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host Seerr

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/seerr-team/seerr:v3.5.1
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 5055.

  3. Fill in the secrets

    3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Seerr requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
5055
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Seerr. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Seerr docs page.

Deploy Seerr your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Seerr from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain seerr=app.example.com.

levelrail-cli templates install seerr --name my-seerr

Deploy Seerr with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/seerr/install \
  -d '{
    "name": "my-seerr"
  }'

Seerr configuration

Seerr services

ServiceImagePortsVolumes
seerr ghcr.io/seerr-team/seerr:v3.5.1 5055 config -> /app/config

Seerr environment variables

VariableServiceValue
LOG_LEVEL seerr Preset by the template
PORT seerr Preset by the template
TZ seerr Preset by the template

Ports and volumes

Ports
5055
Volumes
1 named mount: config -> /app/config

Seerr FAQ

How much memory does Seerr need?

The catalog lists about 512 MiB of memory for Seerr.

Does Seerr run on arm64?

For Seerr, an arm64 image is published; amd64 is image published.

What licence is Seerr under?

Seerr is licensed under MIT, which is permissive, with few conditions on reuse.

Does Seerr need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Seerr use?

Seerr listens on port 5055 inside the stack.

Where does Seerr keep its data?

In a named volume: config mounted at /app/config.

Can I deploy Seerr on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Seerr, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/seerr-team/seerr:v3.5.1 is what you deploy there.

levelrail-cli templates install seerr --name my-seerr