With a whole slew of new reasons on why subscribing to streaming services WILL give you worse services than NOT subscribing to them, i think it’s time to write a new up-to-date guide on how to install and configure an Arr-Stack + SABnzbd via Docker-Compose.
All these guides assume you have basic knowledge about docker & docker compose. To quickly summarize the methods here:
You either use a webui to manage your docker-compose like Dockge or you create a folder and a docker-compose.yaml for each service listed here and copy the contents of each of them into that docker-compose.yaml; IMPORTANT: You HAVE to name them docker-compose.yaml exactly like that. Do NOT name them radarr.yaml for example. After you created a docker-compose.yaml and filled it with the contents here, you simply run docker compose up -d
I specifically did NOT route all those docker-compose files through a VPN container like Gluetun. In my case i have my Mullvad VPN setup on my router directly and selected the whole server to be tunneled through that VPN.
You can add a VPN container to your setup and route all the docker compose files through that. But i will not go through this on this guide. There are guides out there how to do that and you can even ask any big enough LLM as this isn’t really that complicated.
Just as a simple run through. Install Gluetun as an additional docker container and append network_mode: "container:gluetun"
at the end of every docker-compose.yaml here according to the gluetun readme. You also have to remove all the ports:
sections in the docker-compose.yamls of each service because it will throw an error if you use the network_mode:
and you then have to add the ports of each service into the gluetun docker-compose.yaml.
You can then start a console for each docker container and check if the outside world IP adress is NOT your real one with curl ipinfo.io
For every configuration step in this guide where it says “ipofyourserver” for sonarr, radarr, etc. you will have to change that to 127.0.0.1
as they all run inside the same network of gluetun.
This is a super super quick run through and you HAVE to properly configure gluetun and run tests that stopping that container does NOT let your real IP go through.
If you want to store all your media on a NAS or some other external drive, make sure it is configured properly for symlinking / hardlinking and that you have proper permissions for this storage. Everything here will run with the 1000 user and has to create new files to work.
So this is the folder structure i use. And it is stored on a NFS-Share coming from my TrueNAS.
arr-stack (for this example let's say it's located in /mnt/arr-stack)
|---- media
|---- movies
|---- shows
|---- music
|---- etc.
|---- configs
|---- radarr
|---- sonarr
|---- SABnzbd
|---- etc.
|---- nzb
|---- watchfolder
|---- movies
|---- shows
|---- music
|---- etc.
|---- complete
|---- incomplete
I intentionally broke out the nzb folder to make it easier accessible for the watchfolder and/or if you download something fully manual and you want to grab it out of the ‘completed’ folder without searching too deep.
SABnzbd is the download application for Usenet. Alternatively you can use NZBget but i find Sab to be more modern, versatile and i just like it.
services:
arch-SABnzbd:
ports:
- 8080:8080
- 8090:8090
container_name: SABnzbd
volumes:
- /mnt/arr-stack:/arr-stack
- /mnt/arr-stack/configs/SABnzbd:/config
- /etc/localtime:/etc/localtime:ro
environment:
- PUID=1000
- PGID=1000
image: binhex/arch-SABnzbd
restart: unless-stopped
networks: {}
Radarr and Sonarr are the applications that will actually find and track your Movies (Radarr) and Shows (Sonarr). Additionally there is Lidarr for Music and Whisparr for porn.
services:
arch-radarr:
ports:
- 7878:7878
container_name: radarr
volumes:
- /mnt/arr-stack:/mnt/arr-stack
- /mnt/arr-stack/configs/radarr:/config
- /etc/localtime:/etc/localtime:ro
environment:
- PUID=1000
- PGID=1000
image: binhex/arch-radarr
restart: unless-stopped
networks: {}
services:
arch-sonarr:
ports:
- 8989:8989
- 9897:9897
container_name: sonarr
volumes:
- /mnt/arr-stack:/mnt/arr-stack
- /mnt/arr-stack/configs/sonarr:/config
- /etc/localtime:/etc/localtime:ro
environment:
- PUID=1000
- PGID=1000
image: binhex/arch-sonarr
restart: unless-stopped
networks: {}
Prowlarr is the application where you can configure your usenet sites. There you will put in the URLs of your Indexers like Drunkenslug and your API keys for those sites. Prowlarr will periodically check the availability of those services and will sync these accounts to all your connected services (Radarr, Sonarr, Lidarr, Whisparr, etc.). Prowlarr will then be doing the actual heavy lifting of accessing the API of any Usenet and search for your stuff.
services:
arch-prowlarr:
ports:
- 9696:9696
container_name: prowlarr
volumes:
- /mnt/arr-stack/configs/prowlarr:/config
- /etc/localtime:/etc/localtime:ro
environment:
- PUID=1000
- PGID=1000
image: binhex/arch-prowlarr
restart: unless-stopped
networks: {}
Now that we have all these Services up and running. It’s time to properly configure them. Let’s start with SABnzbd
The same procedure goes for Lidarr and Whisparr aswell with their respective categories changed.
Prowlarr will now test and sync the indexers to your other apps like Sonarr and Radarr. Manually click on Test all Inders and then on Sync all Indexers. Now go back to Sonarr and Radarr and click on Settings -> Indexers and check if Drunkenslug (in our example) shows up there.
Now this is obviously just the tip of the iceberg. You still don’t have “finetuned” profiles and explaining these would absolutely blow up the scope of this post.
I highly recommend you to check out these two posts over on the trash-guides site: Sonarr Profiles and Radarr Profiles
Also if you still don’t have a working indexer and just read this guide out of interest you have to actively search for them. Usenet servers like the ones i listed earlier are always open to register. Indexers however are not. Most of them are private and closed and only let you in on a few days per year or if you get an invite from another user.
There are some communities that revolve around sharing invites. You will find them with looking for “usenet invites”
So, these are the basics and there is much more to finetune. But as soon as you have an invite and registered for a host you absolutely are ready to go sailing on the high seas!
If you’re looking for a neat mobile app to manage your sonarr, radarr and sabnzbd i highly recommend you check out nzb360.
Here is an alternate guide on how to set it up using qBitTorrent for torrents: https://lemmy.dbzer0.com/post/26293605
Part 2 of this Guide is aiming for Jellyfin + Jellyseer: https://lemmy.dbzer0.com/post/26296377
1. Posts must be related to the discussion of digital piracy
2. Don’t request invites, trade, sell, or self-promote
3. Don’t request or link to specific pirated titles, including DMs
4. Don’t submit low-quality posts, be entitled, or harass others
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
Daym, MVP (post and person) right here
I am inspired. Will see to my own stack tomorrow.
Great guide, especially the folder structure setup, I wasted so much storage getting that wrong at first.
But im wondering why not put everything into one compose file? It might just be personal preference but I find it a little easy to find what I’m looking for.
(Also this is just a nit-pick but including the version tag now prompts a warning that it’s deprecated.)