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