Self-host Prowlarr with Levelrail
An indexer manager that syncs your torrent and Usenet indexers across the whole Arr stack.
- AuthorProwlarr
- LicenceGPL-3.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host Prowlarr
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/prowlarr:2.6.5
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 9696.
-
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.
Prowlarr requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 9696
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, 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 9696 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 Prowlarr. 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 Prowlarr docs page.
Deploy Prowlarr your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Prowlarr from the CLI
levelrail-cli templates deploy prowlarr --name my-prowlarr Deploy Prowlarr with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/prowlarr/deploy Prowlarr configuration
Prowlarr services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| prowlarr | lscr.io/linuxserver/prowlarr:2.6.5 | 9696 | prowlarr_config -> /config |
Prowlarr environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | prowlarr | Preset by the template |
| PUID | prowlarr | Preset by the template |
| TZ | prowlarr | Preset by the template |
Ports and volumes
- Ports
- 9696
- Volumes
- 1 named mount: prowlarr_config -> /config
Prowlarr FAQ
How much memory does Prowlarr need?
The catalog lists about 256 MiB of memory for Prowlarr.
Does Prowlarr run on arm64?
For Prowlarr, an arm64 image is published; amd64 is image published.
What licence is Prowlarr under?
Prowlarr is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Prowlarr need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Prowlarr use?
Prowlarr listens on port 9696 inside the stack.
Where does Prowlarr keep its data?
In a named volume: prowlarr_config mounted at /config.
Can I deploy Prowlarr 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 Prowlarr, 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/prowlarr:2.6.5 is what you deploy there.