Skip to content

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

Published by Dr_Frankenstein
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 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.

AppAddress (not https://)
Lidarrhttp://NASIP:8686
Radarrhttp://NASIP:7878
Sonarrhttp://NASIP:8989
Readarrhttp://NASIP:8787
Bazarrhttp://NASIP:6767
Prowlarrhttp://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.

AppRoot Folder
Lidarr/data/media/music
Radarr/data/media/movies
Sonarr/data/media/tv
Readarr/data/media/books
BazarrNot required
ProwlarrNot required

Permission Issues (User ABC doesn’t have permission to access folder)

If you get this error when trying to add your Root folders check the following:

  • Your PUID and PGID are set correctly and the right way round in the compose
  • The ‘dockerlimited’ user has read and write permissions showing in the Control Panel > Shared Folders > Permissions
  • If the above has not worked go back to the User creation guide and see the section ‘Permission Fixes – only use if you have issues‘ for a couple of commands that will fix things.

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.

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.

Published inMedia Management 7.2

199 Comments

  1. Mike Mike

    So I am new to all this, I understand the guide but the arr’s are a bit confusing. Which one of these actually do the downloading, or none of them are, do we need something like qbittorrent to do the downloading? not using usenet.

    Also secondary question, is it possible to tie in real-debrid to the downloader?

    # 1 January 2024 Reply
    • Dr_Frankenstein Dr_Frankenstein

      Hey so the Arrs are purely for Media organisation and automation. The workflow looks like this assuming you have added a downloader and indexer(s) to the mix.

      Radarr searches your indexers for the request movie (either via you clicking to search or its automated RSS feeds)
      >
      The results are parsed and checked against your criteria (Profiles/Custom Formats/Size)
      >
      The matching torrent is sent to qBittorrent (Radarr watches its progress)
      >
      On completion / moving to Seeding Radarr ‘moves’ and renames the file to its final folder.

      There is no real-debrid support built in, I have seen mentions of third party tools to try to tie it in, have a search on Reddit..

      https://wiki.servarr.com/

      # 2 January 2024 Reply
  2. cj2peter cj2peter

    I am having trouble linking the Arrs to Deluge or the Arrs are not finding torrents. I have everything set up as far as I can tell. The Deluge connection in Radarr, for example, is successful. I can request movies through Overseerr and see them in Radarr. Deluge never seems to do anything, though. It is like I missed a step somewhere but cannot figure it out. I do see some errors in the logs for the Deluge and Radarr containers but they do not seem to be related.

    Can you point me in the right direction? Any help would be greatly appreciated!

    # 21 December 2023 Reply
    • Dr_Frankenstein Dr_Frankenstein

      Hey

      The only bit you could be missing is adding Indexers to the Arrs in order for them to search for torrents to grab. Have you added any?

      # 22 December 2023 Reply
      • cj2peter cj2peter

        That appears to be the case; Radarr and Sonarr do not have any indexers set up. I guess I assumed Overseerr was the indexer because it is in the Search / Indexers section of the tutorials. Do you have a recommended set of indexers to set up?

        # 23 December 2023 Reply
        • Dr_Frankenstein Dr_Frankenstein

          I can see that being confusing, I will split so its Indexers and Frontends or something similar… Are you using Torrents or Usenet?

          # 23 December 2023 Reply
          • cj2peter cj2peter

            I’m not really sure what the difference is or how to choose. I tried setting up some free torrent indexers but Prowlarr doesn’t want to sync to Radarr or Sonarr.

            # 23 December 2023 Reply
            • Dr_Frankenstein Dr_Frankenstein

              Hey sorry I skipped your comment, does your ISP block access to any indexers as that will cause issues.

              Usenet will be if you want to pay for a monthly/annual service to access as well as requiring a decent paid for indexer. Torrents on the other hand are free.

              # 26 December 2023 Reply
  3. kl4xxo kl4xxo

    hi followed all but getting the error error response from daemon /volume1/data does not exist . but it really does dockerlimited has read write permissions to data folder and docker folder

    # 10 December 2023 Reply
  4. Littlepasty Littlepasty

    Hey Dr Frankenstein is there a way to create extra versions of Radarr and Sonarr to handle just 4k content? I like to keep these separate so that I can keep both HD and 4k content

    # 7 December 2023 Reply
    • Dr_Frankenstein Dr_Frankenstein

      Hey

      Yes you will create a separate folder for the config folder such as /docker/radarr4k
      Then you will amend the external port for the WebUI which is the left hand port in the yaml leaving the right side one the same.

      # 7 December 2023 Reply
      • Littlepasty Littlepasty

        Thank you so much!
        I was stuck on the port assigning in the yaml, time to have well organised media!

        # 9 December 2023 Reply
  5. GarlicRagu GarlicRagu

    For whatever reasoning can never get bazarr working. I’ve used your guide to set it up before with no luck. I’ve since tried this project method and still no luck. Every other arr is functional but when I go to my localip:6767 I receive a site can’t be reached error. Every other port works but bazarr gives me nothing but trouble. I’ve double checked the bazarr section of the YAML and it all looks correct. It uses the same PUID, PGID, and TZ as the others. I don’t know what else could be causing this issue or where to start looking. Any advice is appreciated.

    # 3 December 2023 Reply
    • Dr_Frankenstein Dr_Frankenstein

      Hey, have a look at the logs for the Bazarr container to see what it is doing, it should usually highlight an issue with start up.

      # 3 December 2023 Reply

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!