Self-host Sonarr with Levelrail
Watches your favorite indexers for new TV episodes and automatically grabs, sorts, and renames them.
- AuthorSonarr
- LicenceGPL-3.0-or-later
- Memory256 MiB
- Archarm64
- Services1
How to self-host Sonarr
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/sonarr:4.0.12
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8989.
-
Fill in the secrets
3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Sonarr requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8989
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-or-later, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8989 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Sonarr. 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 Sonarr docs page.
Deploy Sonarr your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Sonarr from the CLI
levelrail-cli templates deploy sonarr --name my-sonarr Deploy Sonarr with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/sonarr/deploy Sonarr configuration
Sonarr services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| sonarr | lscr.io/linuxserver/sonarr:4.0.12 | 8989 | sonarr_config -> /config |
Sonarr environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | sonarr | Preset by the template |
| PUID | sonarr | Preset by the template |
| TZ | sonarr | Preset by the template |
Ports and volumes
- Ports
- 8989
- Volumes
- 1 named mount: sonarr_config -> /config
Sonarr FAQ
How much memory does Sonarr need?
The catalog lists about 256 MiB of memory for Sonarr.
Does Sonarr run on arm64?
For Sonarr, an arm64 image is published; amd64 is image published.
What licence is Sonarr under?
Sonarr is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.
Does Sonarr need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Sonarr use?
Sonarr listens on port 8989 inside the stack.
Where does Sonarr keep its data?
In a named volume: sonarr_config mounted at /config.
Can I deploy Sonarr 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 Sonarr, 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 lscr.io/linuxserver/sonarr:4.0.12 is what you deploy there.