Important or Recent Updates
| Historic Updates | Date |
|---|---|
| New guide | 13/09/2023 |
| Added additional security option to the compose to restrict the container from gaining new privileges as well as umask variable | 25/10/2023 |
| Adjusted the restart variable to make sure containers start on boot | 28/10/2023 |
This guide is going to eventually replace the existing separate guides for all the apps in the title. By combining these into a single project it saves you time and effort in the initial set up and makes updates more seamless.
You can add and remove the containers from this project based on your preferences.
Let’s Begin
In order for you to successfully use this guide please complete the three initial setup guides if you have not done so already
- Docker Package, SSD and Memory Recommendations
- Step 1: Directory Setup Guide
- Step 2: Setting up a restricted Docker user
- Step 3: Setting up a Docker Bridge Network (synobridge)
As Container Manager now supports using Docker Compose in the UI we will be using it as it will save you lots of time and steps!
What on earth is a Docker Compose? Docker Compose allows us to define how Docker should set up one or more containers within a single configuration file. This file is yaml formatted and Container Manager uses the Projects feature to manage them.
Folder Setup
First we need to set up some folders for the Arr’s to save their configuration files and also where the Project will save the compose.
Using File Station create the following folders. (Skip ones you don’t need)
/docker/projects/arrs-compose - Required
/docker/radarr
/docker/sonarr
/docker/lidarr
/docker/prowlarr
/docker/bazarr
/docker/readarr
Container Set Up
Next we are going to set up a ‘Project’ in Container Manager. Open up Container Manager and click on Project, then on the right-hand side click ‘Create’.
In the next screen we will set up our General Settings.
| Section | Setting |
|---|---|
| Project Name: | media-project |
| Path: | /docker/projects/arrs-compose |
| Source: | Create docker-compose.yml |
Next we are going to drop in our docker compose configuration, copy all the code in the box below and paste it into line ‘1’
A couple of notes:
- I personally use the Linuxserver images, so they are used below
- I am pulling these images directly from Docker Hub and not lscr.io this is because container manager can’t check for updates on third party sites
- You will see notes saying #change me we will do this on the next step, and you can remove the comments if you wish
services:
sonarr:
image: linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
volumes:
- /volume1/docker/sonarr:/config
- /volume1/data:/data
ports:
- 8989:8989/tcp
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: always
lidarr:
image: linuxserver/lidarr:latest
container_name: lidarr
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
volumes:
- /volume1/docker/lidarr:/config
- /volume1/data:/data
ports:
- 8686:8686/tcp
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: always
radarr:
image: linuxserver/radarr:latest
container_name: radarr
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
volumes:
- /volume1/docker/radarr:/config
- /volume1/data:/data
ports:
- 7878:7878/tcp
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: always
readarr:
image: linuxserver/readarr:develop
container_name: readarr
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
volumes:
- /volume1/docker/readarr:/config
- /volume1/data/:/data
ports:
- 8787:8787/tcp
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: always
bazarr:
image: linuxserver/bazarr:latest
container_name: bazarr
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
volumes:
- /volume1/docker/bazarr:/config
- /volume1/data/:/data
ports:
- 6767:6767/tcp
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: alwaysI have split out Prowlarr as you may want this running on a VPN connection if your ISP blocks certain indexers. If not copy this section into your compose as well. See the side menu for adding this to GlueTUN.
prowlarr:
image: linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
volumes:
- /volume1/docker/prowlarr:/config
ports:
- 9696:9696/tcp
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: alwaysEditing the Compose & Environment Variables
Please keep in mind that YAML formatting is very specific, so keep things lined up as per the original.
The compose contains all the Arr’s in the overall stack, you can remove any you don’t plan on using by deleting their entire section in the code.
We need to make some minor edits to the compose file in order to make sure the containers use the ‘dockerlimited’ user we created earlier and also let them know which timezone we are located. You will need to edit these in each section noted with ‘#change me’
| Variable | Value |
|---|---|
| PUID= | Change it to the UID you obtained earlier in the first setup guides |
| PGID= | Change it to the GID you obtained earlier in the first setup guides |
| TZ= | You will need to change this line to your own timezone code – you can find the correct list of ones to use on wikipedia.org/wiki/List_of_tz_database_time_zones |
Once you have made all your required edits click ‘Next’
Nothing to change on the next screen click ‘Next’ again..
On the final screen just click ‘Done’ and you will see a new window appear which will kick of downloading of the required container image and configure the containers.
This can take a couple of minutes to finish as all the images are downloaded and extracted. You should see ‘Code 0’ when it has finished.
Once finished you will see the Project is running with a green status.
Firewall Exceptions
(Skip if you don’t have the Firewall configured)
If you have the Synology Firewall enabled please see this additional guide for further info on exceptions and correct set up.
Containers are ready to use
You will now be able to access each of the containers on their respective ports.
| App | Address (not https://) |
|---|---|
| Lidarr | http://NASIP:8686 |
| Radarr | http://NASIP:7878 |
| Sonarr | http://NASIP:8989 |
| Readarr | http://NASIP:8787 |
| Bazarr | http://NASIP:6767 |
| Prowlarr | http://NASIP:9696 |
Please see the next section which covers the ‘basics’ of each application setup as these usually catch people out. Full documentation can be found on https://wiki.servarr.com/
Key Settings within the Arrs
Settings > Media Management > Root Folders
Each of the Arr’s refer to the place(s) you keep your media as ‘Root Folders’. These are where the app will ultimately move your music/movies/books/shows once they finish downloading. Use the table below to set each of your folders correctly.
You will see other folders when you first browse for the /data folder it is located in the top level folder.
| App | Root Folder |
|---|---|
| Lidarr | /data/media/music |
| Radarr | /data/media/movies |
| Sonarr | /data/media/tv |
| Readarr | /data/media/books |
| Bazarr | Not required |
| Prowlarr | Not required |
Settings > Media Management > Remote Path Mappings
While most of the settings on this page are self-explanatory something that has caught people out is the Remote Path Mappings setting. If you are hosting all your services on the same NAS and in Docker do not add any settings here.
Settings > Download Client(s) > Add your Client > Host and Port
As our containers are all running on the ‘synobridge’ custom bridge we can use the Gateway IP for this bridge for inter container networking. This will be 172.20.0.1 and the appropriate port for your Client assuming it is running in Docker!
You should now have the basics in place and I 100% recommend having a look at the previously mentioned https://wiki.servarr.com/ documentation as it will help you understand how the Arrs work.
Other settings for the Arrs
While I covered some very basics you really need to make use of the documentation, it goes into detail of how and why the core functions work across the apps. You can find it on the Servarr Wiki.
FAQ
Migration from old guides.
If you followed my older guides where you set up each of these containers in the Container Manager UI or Pre DSM7.2 Docker UI you can follow this one to migrate in a couple of steps.
- Stop and delete the existing containers but keep your directories!
- Follow the rest of this guide and all your existing configs will be kept using your old files.
Looking for some help, join our Discord community
If you are struggling with any steps in the guides or looking to branch out into other containers join our Discord community!
Buy me a beverage!
If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me stay hydrated. Plus 10% goes to the devs of the apps I do guides for every year.
Hello! Any chance for a quick tutorial of adding a second instance of Radarr for 4k movies or different language?
I tried adding another project named media2 with arrs-compose2 folder and new radarr2 folder in docker. New port is 7879.
Container starts without a problem, but browser says the site can’t be reached.
Thank you!
Hey, sounds like you are 99% there, as these are going to both run on synobridge we need to do some swapping about..
On your existing non 4k install go to Radarr Settings > General > Port and change it to 7879 save and then stop the Project, and then edit the ports in line.. 7879:7879
Then put the new 4k install on the old original ports..
It’s working! port has to be 7879:7878
OK cool – I was thinking that as your original Radarr was on 7878 internally that the other could not share it, out of interest are they on independent bridges?
on sonarr, i configured my /share/data/media/:/data but the import doesnt work. im getting an error during import “Import failed, path does not exist or is not accessible by Sonarr: /data/tv/When.the.Phone.Rings.S01E06.Episode.6.1080p.NF.WEB-DL.KOR.AAC2.0.H.264.MSubs-ToonsHub.mkv.”
qbittorrent downloads folder is configured on “/share/data/torrents:/data”
what could be the problem?
Hi Ryan – spotted you posted on Discord so we can fix directly – for anyone else reading this in the future make sure the mount points match up as with the above Sonarr can’t reach across into the completed folder
/share/data/media/:/data
/share/data/:/data
First of all, thanks for all the information you provide.
I attempted to follow your instructions and am unable to get connected to the indexers in prowlarr. Prowlarr is connected to Lidarr, Sonarr, Radarr and passes the “test”, here is an example of the error message I am getting in prowlarr —
Invalid request Validation failed:
— : Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. Resource temporarily unavailable (badasstorrents.com:443)
In addition to your tutorial I am using protonVPN and followed their tutorial here — https://protonvpn.com/support/synology/
Thanks!
Hi Brett – Can you first try without the VPN enabled to see if the error persists, then also within DSM Networking settings for your connected LAN port disable IPv6. You may need to restart the Project.
Keep in mind that connecting the whole system to the VPN won’t protect you if it drops out, you could leak information if a torrent client is not bound to a VPNs TUN device. You may want to have a look at GlueTUN. We have lots of people using it successfully on Discord. I can post up and example compose if you need it.
The indexers do not error in prowlarr after turning off the VPN in the NAS network settings. I have prowlarr connected to lidarr and it did not appear requests from lidarr were being sent over to qbittorrent.
I am new to this so the glue TUN and qbittorrent tutorial was a little intimidating and I wanted to see if I could get your qbittorrent tutorial to “work” before attempting the glueTUN + qbittorrent.
I would give the qbit/gluetun a go as its going to be difficult to know why it fails when the overall DSM VPN is enabled. It could be due to docker itself not being able to access the internet, maybe. When the VPN is turned on do the Arrs function e.g. adding a new artist, movie etc or do you get time-outs.
I was able to have gluetun show as “healthy”. A movie request from radarr showed up in the deluge download area but did not progress.
There is nothing from lidarr populating in the download section of deluge.
Does the torrent have any seeds shown within Deluge? Test the connection using something like the Ubuntu torrent to see if you are connected.
https://ubuntu.com/download/alternative-downloads
Try triggering a manual search for an album in Lidarr so it lets you choose a release – it will also show a red ! for anything not meeting your requirements. Which would result it nothing being sent to Deluge.
I pasted the link to “Ubuntu 24.10 Desktop (64-bit)” into the add url in deluge and it shows up in the download queue. At the bottom it lists Seeds: 0 (1217) and Peers: 65 (318).
After ~10 minutes it did not download anything and then errored.
[SNIP]
2024/12/04 15:22:57 stdout User GID: 1028
2024/12/04 15:22:57 stdout User UID: 65537
2024/12/04 15:22:57 stdout
2024/12/04 15:22:57 stdout ───────────────────────────────────────
2024/12/04 15:22:57 stdout GID/UID
2024/12/04 15:22:57 stdout ───────────────────────────────────────
[/SNIP]
Ah, I see the issue – Your GID and UID (PGID and PUID) are the wrong way around 🙂
I was able find out how to manually request a torrent in lidarr. I was able to get one downloaded but none have crossed over from the monitored/ ‘”wanted” section. Seems I do not have great indexers selected for music…
I disabled the VNP from the network connections and the indexers worked.
I followed the instructions on the gluetun + deluge tutorial.
Is there a way to “test” to make sure the VPN is working before attempting to download a torrent?
Thanks
Ha, sorry just realised I replied to your earlier comment (working oldest to newest) Deluge or any other container connected to GlueTUN will have its network connection dropped if the VPN disconnects (The connection is firewalled by GlueTUN) so effectively a killswitch. The GlueTUN log will show its connected and healthy.