Skip to content

Arr’s Media Project – Radarr, Sonarr, Lidarr, Prowlarr, Bazarr, Readarr in Container Manager on a Synology NAS

Important or Recent Updates
Historic UpdatesDate
New guide13/09/2023
Added additional security option to the compose to restrict the container from gaining new privileges as well as umask variable25/10/2023
Adjusted the restart variable to make sure containers start on boot28/10/2023
Historic Updates

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.

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.

  1. Stop and delete the existing containers but keep your directories!
  2. Follow the rest of this guide and all your existing configs will be kept using your old files.

Settings for the Arrs

While I cover some very basics towards the end of the guide 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.

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

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)

Folders
/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.

SectionSetting
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
YAML
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: always

I 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 my Gluetun guides for more information on adding to a VPN.

YAML
  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: always

Editing 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’

VariableValue
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
Key Edits

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 enabled and configured the Synology Firewall you will need to create exceptions for any containers that have a Web UI or have any incoming or outgoing connections. This section covers the basics of how to add these. (Please note this is a generic section and will not show the specific ports used in this guide however it applies in the same way)

Also, I would like to refer people to the great guide on getting the Firewall correctly configured over on WunderTechs site.

Head into the Control Panel> Security > Firewall, from here click Edit Rules for the profile you set up when you enabled the Firewall.

Next click on Create and you will see the screen below. Source IP and Action will be automatically selected to All and Allow, I will leave it up to you as to your own preference on whether you want to lock down specific Source IPs from having access. In this example we will leave as All.

You will now choose ‘Custom‘ and then the Custom button

Now select Destination from the drop-down menu, most web based containers require TCP access but check the guide as it will show the port and protocol. Then add comma separated ports. Then press OK.

Click OK a couple of times to get back to the main screen. You will see by default the new rule is added to the bottom of the list. You must always have your Block All rule last in the list as the rules are applied top down so move your container up.

You have now completed the Firewall changes and can continue with the guide.

Containers are ready to use

You will now be able to access each of the containers on their respective ports.

AppPort used
LidarrNASIP:8686
RadarrNASIP:7878
SonarrNASIP:8989
ReadarrNASIP:8787
BazarrNASIP:6767
ProwlarrNASIP: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.

AppRoot Folder
Lidarr/data/media/music
Radarr/data/media/movies
Sonarr/data/media/tv
Readarr/data/media/books
BazarrNot required
ProwlarrNot 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.



Buy Me a Coffee or a Beer

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 get the odd beverage. Plus 10% goes to the devs of the apps I do guides for every year.

Published inMedia Management 7.2

125 Comments

  1. chris chris

    Hey ! thx you for your guide !
    Very noob question.

    Do we need to keep all these services behind a VPN ? or the only service behind the VPN should be the “downloader” (qBittorent in my case) ?

    In either way, can we you this guide with qbitorrent being behind a vpn ? (from one of your other guides), or do we need to change stuff ?

    Thx you !

    • Dr_Frankenstein Dr_Frankenstein

      Hey so no need for the Arr’s to be behind the VPN so you can do this setup and the GlueTUN and Qbit setup independently and they can all talk to one another.

    • Dimfil Dimfil

      You can keep *arr apps and nzb downloaders out of vpn but keep torrent downloaders (Qbittorrent/Deluge) and indexer managers (Prowlarr/Jackett/NZBHydra2) in Gluetun’s docker compose.
      It will save you from a lot of troubles and speed issues as providers have started to struggle torrents and indexers as much as possible!

      Just my 2c…

  2. Mal Mal

    I have been super impressed by this guide and have successfully built my homelab following your instructions … so firstly thanks!!

    Do you use a Homepage/Dashboard tool that pulls all this together into a single interface?

    I’d be interested to know your preference and even more keen to see the installation instructions 🙂

    • Dr_Frankenstein Dr_Frankenstein

      Hey, I have tried a few over the years I am currently using Flame just as its nice and simple with just links. I know some people use Homepage, Homer etc. Check the github page for the one you want use and generally they have a compose file which you can essentially compare to how the ones work on here. Feel free to message me if you get stuck. I need to start work on a couple of new guides.

      • Mal Mal

        Hiya – I tried Flame and homepage but didn’t like them so went for Homarr in the end … which I really like.

        As a form of giving back, this is the YAML I used which worked v well within the ecosystem you have guided me to !!

        version: ‘3’
        #———————————————————————#
        # Homarr – A simple, yet powerful dashboard for your server. #
        #———————————————————————#
        services:
        homarr:
        container_name: homarr
        environment:
        – PUID=1234 #CHANGE_TO_YOUR_UID
        – PGID=56789 #CHANGE_TO_YOUR_GID
        image: ghcr.io/ajnart/homarr:latest
        restart: unless-stopped
        volumes:
        – /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
        – /volume1/docker/homarr/configs:/app/data/configs
        – /volume1/docker/homarr/icons:/app/public/icons
        – /volume1/docker/homarr/data:/data
        ports:
        – ‘7575:7575’
        network_mode: synobridge
        security_opt:
        – no-new-privileges:true

        Thanks Dr_F

        • Dr_Frankenstein Dr_Frankenstein

          Thanks for this. I have started working on some new guides after a break, aiming to get one out every couple of weeks (but limited to the ones I am using)

  3. Ryan Ryan

    Good morning and THANK YOU!!!!

    Another question…

    After getting all the Arrs up and running, the final step has got me perplexed… adding download clients.

    I assume I choose Torrents\Deluge since that is the Project I created using this guide with Deluge & AirVPN.

    I am changing the host to 172.20.0.1, but am getting an authentication error with the password already filled in. I have tried the dockerlimited password with no luck. When launching all the Arrs for the first time, I was forced to create remote user account, which I used the same credentials for all the Arrs. I chose to disable authentication for Local Addresses.

    Thoughts?

    • Dr_Frankenstein Dr_Frankenstein

      Hey

      So the deluge password will be whatever you set it to when you went through the guide. It’s not the password for the dockerlimited account. The arrs do now force you to create logins for them due to the amount of people exposing them to the internet without login details!

  4. R2SB R2SB

    Hey mate, thanks for all these guides. I’ve set up the docker user & group as you set out, but when I spin the aars up, they all have a line in the log that says “[Info] AppFolderInfo: Data directory is being overridden to [/config]”. The app still deploys, but the internal /data folder is empty.

    Their volumes are all set up like this:
    volumes:
    – /volume1/docker/sonarr:/config
    – /volume1/data/:/data
    I tried it like this too:
    – /volume1/docker/sonarr:/config
    – /volume1/data:/data

    I’m pretty sure I have the folder permissions set correctly (your other guides have worked as they should)

    Any ideas? Thanks again!

    • Dr_Frankenstein Dr_Frankenstein

      Hey

      Triple check the PUID/PGIDs are correct as this is the no1 reason for issues usually. Failing that can you jump back to the User and Group guide, at the bottom you will see some permissions fix commands.. Odd that it would just be one of them playing up!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

drfrankenstein.co.uk – writing Synology Docker Guides since 2016 – Join My Discord!