The *arr Stack: Automate Your Media Library
How Sonarr, Radarr, Prowlarr and a download client work together to build a hands-off media server, with a working Docker Compose layout, folder structure and troubleshooting tips.
What is the *arr stack?
The "*arr" apps are a family of open-source tools that automate finding, downloading and organizing media. Together they turn a media server into a hands-off system: you request a title once and it appears, correctly named and sorted, in Jellyfin or Plex.
The core pieces:
- Sonarr — manages TV shows and grabs new episodes as they air.
- Radarr — does the same for movies.
- Prowlarr — a single place to manage your indexers, syncing them to Sonarr and Radarr so you configure each source only once.
- A download client — the app that actually fetches files, such as qBittorrent or SABnzbd.
- Jellyseerr — the request portal your household uses. See our Jellyseerr setup tutorial.
- Optional extras: Lidarr for music, Readarr for books, Bazarr for subtitles.
How the pieces fit together
- A user requests a movie in Jellyseerr.
- Jellyseerr tells Radarr to add it.
- Radarr searches your indexers (configured via Prowlarr) for a release matching your quality profile.
- Radarr sends the chosen release to your download client.
- When the download finishes, Radarr imports it — renaming and moving (or hardlinking) it into your library folder.
- Jellyfin or Plex picks up the new file and it is ready to watch.
Every app talks to the others through a URL and an API key. Understanding that one idea makes the whole stack much easier to troubleshoot: when something is not working, one app cannot reach another, or has the wrong key.
Folder layout matters more than anything
A consistent layout is the single most important part of a reliable setup. Use one top-level folder that contains both downloads and your final library:
/data
├── downloads
│ ├── torrents
│ └── usenet
└── media
├── movies
└── tvMount that same /data folder into every container (the download client, Sonarr, Radarr and your media server). When downloads and media share a filesystem and the same container path, the *arr apps can use hardlinks: the finished file appears in your library instantly, uses no extra disk space, and keeps seeding from the download folder. If you mount downloads and media as separate volumes, imports become slow copies and use double the space.
A starting Docker Compose file
This example uses the widely used LinuxServer.io images. Adjust paths, time zone and user IDs. Check your user and group IDs with id.
services:
prowlarr:
image: lscr.io/linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Berlin
volumes:
- ./prowlarr:/config
ports:
- "9696:9696"
restart: unless-stopped
sonarr:
image: lscr.io/linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Berlin
volumes:
- ./sonarr:/config
- /srv/data:/data
ports:
- "8989:8989"
restart: unless-stopped
radarr:
image: lscr.io/linuxserver/radarr:latest
container_name: radarr
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Berlin
volumes:
- ./radarr:/config
- /srv/data:/data
ports:
- "7878:7878"
restart: unless-stopped
qbittorrent:
image: lscr.io/linuxserver/qbittorrent:latest
container_name: qbittorrent
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Berlin
- WEBUI_PORT=8080
volumes:
- ./qbittorrent:/config
- /srv/data/downloads:/data/downloads
ports:
- "8080:8080"
restart: unless-stoppedNote that in the example the download client mounts /srv/data/downloads at /data/downloads, matching the path the other containers see. The important point is that the path inside the containers is identical, so Radarr and Sonarr can find what the download client reports.
Put the containers on the default Compose network so they reach each other by service name, for example http://radarr:7878 and http://qbittorrent:8080. Read Docker networking explained if container networking is new to you, and Docker Compose best practices for pinning versions and keeping secrets out of the file.
Configuration order that works
Set the apps up in this order to avoid circular confusion:
- Download client: create a username and password and set the default save path to
/data/downloads. - Prowlarr: add your indexers, then add Sonarr and Radarr as "Apps" using their URLs and API keys. Prowlarr pushes the indexers to them automatically.
- Radarr and Sonarr: add the download client under Settings → Download Clients, then set the root folders to
/data/media/moviesand/data/media/tv. - Enable hardlinks and renaming under Settings → Media Management, so imports use the correct names.
- Jellyseerr: connect it to your media server and to Radarr and Sonarr.
- Media server: add
/data/media/moviesand/data/media/tvas libraries.
Quality profiles: the key concept
Quality profiles tell Sonarr and Radarr what you actually want — for example "1080p, but upgrade to 4K if available, and never grab anything above 20 GB for a movie." Spend time here; good profiles prevent both grainy files and 80 GB monsters that fill your disks. Start with a simple profile, watch what it picks for a week, then refine. Community guides such as TRaSH Guides publish well-tested profile and naming recommendations.
Common problems and fixes
- "Download client unavailable" or "Unable to connect": use the container name, not
localhost, as the host in Sonarr or Radarr, and confirm the port and credentials. - Imports fail with "No files found" or a path error: the download client and the *arr app see different paths. Fix the volume mounts so both use
/data/.... - Imports are slow and use double disk space: downloads and media are on different filesystems or mounted separately. Use a single
/datamount. - Permission denied: make sure all containers run with the same
PUIDandPGIDand that the folders are owned by that user. - Nothing is ever grabbed: check that indexers are synced from Prowlarr, and that your quality profile and minimum availability allow the release you want.
Run it reliably
Add Portainer if you prefer a UI for day-to-day container management and Uptime Kuma to monitor each service. Back up the config folders of every app (they hold your settings, history and API keys), not the media itself, following our backup strategy guide. A rebuild then takes minutes.
Keep the stack private. Do not expose Sonarr, Radarr, Prowlarr or your download client directly to the internet. Reach them through a VPN such as Tailscale or WireGuard, and if you publish only Jellyseerr, put it behind a reverse proxy with HTTPS and authentication.
A note on responsible use
Use the *arr stack with content you are legally entitled to — for example, managing your own library, public-domain media, or legitimate sources. Always follow the laws in your country.
Where to go next
Once the stack runs smoothly, tune it with quality profiles, add subtitle automation with Bazarr, and consider hardware transcoding in your media server. Our Jellyfin tutorial covers the media server side, and the hardware guide helps you plan storage capacity for a growing library.
Verwandte Artikel
Plex vs. Jellyfin
Plex vs. Jellyfin im Vergleich: Funktionen, Hardware-Transcoding, Datenschutz, Kosten und welcher Medienserver zu dir passt.
Jellyfin-Medienserver einrichten
Installiere Jellyfin mit Docker und streame deine Filme, Serien und Musik kostenlos auf alle Geräte.
How to Set Up Jellyseerr for Media Requests
Install Jellyseerr with Docker, connect it to Jellyfin, Sonarr and Radarr, and set up users, quotas and approvals so your household can request media on its own.