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.

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

165 Comments

  1. Michael Michael

    “I know this sounds extreme but can you try re-installing the Container Manager package – when uninstalling it will give you the option to keep all the configs/share – say yes to keep them and then reinstall the package again.”

    couldnt reply to your answer, so i write it here as a new comment.

    Reinstalled the container. kept every setting as you proposed, restarted the nas, still the same error -.-

    i may go with hte host option for now and guess i will go into the discord tomorrow, unless you find anything else to try.

    • Dr_Frankenstein Dr_Frankenstein

      I think we hit the thread limit, Something is broken or blocking the connection as this should just work without issue. Roll with host for the time being, so you can start getting set up and either ping me an email via my contact page or jump on Discord, so we can dig deeper.

  2. Michael Michael

    I have some troubles with the arrs. If i search for something or try to import movies, i dont get any results. I made some reading myself and it seems to be a DNS issue.

    I set everything up like your guides, gluetun VPN with qbit and prowlarr (the searching for torrents within prowlarr works), Adguard with Macvlan.

    I can access the radarr sites from my browser (for example: https://radarrapi.servarr.com/v1/movie/5548 ), so its not an issue with my router (not a Unify router), my provider or adguard, as then i wouldnt be able to access this site. I am also not located in Russia or route my traffic in some way through russia

    I also do not have https or a reverse proxy within my network.

    I am not sure where exactly the problem lies. Given from what i read it seems to be a DNS problem and i would point the cause somewhere towards docker.

    I can also provide some logs: https://pastebin.com/cVcFNhFg

    Thank you

    • Dr_Frankenstein Dr_Frankenstein

      Hey, it’s always DNS!

      Have you tried just doing a reboot of the NAS before you spend hours chasing your tail, I have seen this before so start with that..

      • Michael Michael

        Yes, 2 times. I just did another restart of the NAs and also of my Router and still the same error.

        • Dr_Frankenstein Dr_Frankenstein

          Can you try amending the network mode of Radarr to

          network_mode:host and see if you get it going.

          • Michael Michael

            sorry for the late reply.

            Changing it to host solved the issue. Whats the best step forward? Keep it at host or is there anything else i can do?

            Thanks again

            • Dr_Frankenstein Dr_Frankenstein

              Do you have anything else on the Synobridge as it must not have created correctly. I would try to remove it and re-add it again. You will likely need to stop and remove any containers attached to it… Should be as simple as stopping the projects.

                • Dr_Frankenstein Dr_Frankenstein

                  I thought (seemingly imagined) you mentioned not having the Firewall on, is that the case?

                  • Michael Michael

                    I usually have it on, but also turned it off several times and it made no difference.

                    Regading your other question, i have nothing on the synobridge except gluetun and the arrs.

                    I also just restarted my nas for good measure and it made no difference. Still getting the same error

                    • Dr_Frankenstein Dr_Frankenstein

                      I know this sounds extreme but can you try re-installing the Container Manager package – when uninstalling it will give you the option to keep all the configs/share – say yes to keep them and then reinstall the package again.

    • Dr_Frankenstein Dr_Frankenstein

      Hey I will pop it on the list – I do have it set up locally – If you are on Discord we have a setup thread..

  3. Rey Rey

    I am not able to setup any of the root directories. When I try to set them up in the respective arrs app I get a message stating that the directory does not exist. If I browse to the /data/ dir on each of either of them it is empty. The share is setup with the correct permissions and sub folders as you mentioned in the guide.

    • Dr_Frankenstein Dr_Frankenstein

      OK this will be a permissions issue – check that your PUID and PGID are correct and the right way around.

      If they are and you are still struggling come back and I can share a command to run to fix the permissions which I will be adding to the FAQ shortly.

  4. lan lan

    Thanks for the great guides, very helpful.

    Is it possible to run a second instance of radarr? I’ve tried by making a new project/container with the same yml as I did for my initial radarr, but using a different port and any mention of radarr changed to radarr_4k.

    It builds without any issues but I cannot access it and instead get a “This site can’t be reached. The connection was reset” error when trying to open it.

    • Dr_Frankenstein Dr_Frankenstein

      Hey yes deffo.

      You are on the right track, when amending the ports for the second instance the internal port will remain the same you just amend the external to a custom one.

      ports:
      external(change):internal(keep the same)

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!