Skip to content

Sonarr in Docker on a Synology NAS

Added Docker Compose details
Added new folder mappings to ensure atomic moves and Hard-linking
Guide re-written and updated with DSM7 screenshots 01/08/2021
Updated wording in some sections and updated the Docker Compose16/12/2021

What is Sonarr?

Sonarr is used to search, download and organise your TV shows in conjunction with your preferred Usenet or Torrent downloaders and indexers.

Lets Begin

In this guide I will take you through the steps to get Sonarr up and running in Docker.

In order for you to successfully use this guide please complete the two preceding guides

Downloading the Sonarr Image

Open up Docker within DSM and navigate to the ‘Registry’ tab and search for ‘Sonarr’.

In the list of available containers select the one made by Linuxserver as shown below, right click on it and select ‘Download’ or click the button at the top of the window.

When the dialogue pops up asking you to choose a version, make sure you choose ‘Latest’ from the list.

You can check the status of the download over on the ‘Image’ tab.

Setting up the container

In Docker click on the ‘Image’ tab, in the list of your containers select the ‘Linuxserver Sonarr’ image and click on ‘Launch’

You will now see the initial setup screen, if you want to you can change the name of the container to something else.

You will also notice a Configure capabilities button — don’t change anything in here!

Next up we are going to click on the ‘Advanced Settings’ button, this will take you to a new window with a number of tabs which we are going to work through.

On the first tab enable ‘Auto Restart’ this will ensure Sonarr will automatically start up whenever you reboot your NAS.

Volumes / Mounts

We can now move onto the volume tab in which we will be specifying the directories where Sonarr will store its configuration files and where to find our media and downloads

Click on Add Folder, click on the docker folder and create a new sub-folder called ‘sonarr’ select this folder and click ‘select’

Now add ‘/config’ to the ‘Mount path’ box

Click Add Folder again and this time select the top level ‘data’ folder and click Select.

You will now enter ‘/data’ into the ‘Mount path’ box

Your path settings should now look like the table/screenshot below.

File/FolderMount path


We are not going to be specifying specific ports for Sonarr to use as we want to keep things simple, tick the ‘Use the same network as Docker Host’

You do not need to set up anything on this tab.

Environment Variables (PGID,  PUID and Timezone)

Next we are going to set up a couple of environment variables that docker will use to allow the container access to our files and folders and also to tell it where we live in the world.

Click the Add button, and fill in the following details as per the table/screenshot, you will need to do one at a time.

PUIDThe UID you obtained in the user setup guide
PGIDThe GID you obtained in the user setup guide
TZYour timezone

Almost Done

You have now completed the setup of the container.

Click on Apply to move back to the initial settings screen and then click next, you will be shown an overall summary of the settings we have specified, this is a good time to double-check everything is correct. Finally, click on Done and the container should start to boot.

You should now be able to access Sonarr via the IP of your NAS followed by the port 8989


Make sure you check out page 2 of this guide that covers some common basic settings.

Docker Compose

You can use the below code saved as sonarr.yml in the ‘/docker/sonarr’ share, this will do the entire process above in one quick command via SSH. Ensure you change the variables to your own.

version: "3.8"
    image: linuxserver/sonarr:latest
    container_name: sonarr
      - TZ=Europe/London
      - /volume1/docker/sonarr:/config
      - /volume1/data:/data
    network_mode: host
    restart: unless-stopped
sudo docker-compose -f /volume1/docker/sonarr/sonarr.yml up -d

Throw me some bits or buy me a coffee?

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running the site, you can even buy me a coffee 🙂

Buy Me A Coffee
Doge / Ethereum / Bitcoin

Pages: 1 2

Published inDockerSynology


  1. Jim Jim

    Hi – thank you for this great write up. It got me up and running with Sonarr in minutes.

    I do have one question (apologies if I just missed this in the directions, or if I missed a setting in the Sonarr UI):

    I’m on a Synology 920+, running Sonarr in Docker and Download Station natively, with Plex as my media server.

    Using your instructions, I’m able to add shows to Sonarr and have them automatically download to my Downloads folder (default location for Download Station).

    However, the show then just sits in the Downloads folder (/volume1/Downloads). How do I tell Sonarr to move it to my Plex library (/volume1/video/TV Shows)?

    I’ve enabled “Rename Episodes” and “Use Hardlinks” in the Sonarr UI. Do I need to do something with “Remote Path Mappings”? Or is it a directory/permissions setting in Docker?

    I’m guessing that somewhere in the workflow I need to tell Sonarr where to move the completed download, and I’m not sure how or where to do that.

    Appreciate the help!

    • Jim Jim

      OR – am I approaching this backwards and instead of pointing Sonarr to my Plex TV folder (/volume1/video/TV Shows), I need to point my Plex TV folder to Sonarr (data/media/tv)? And copy all of my existing Plex TV files over to that data folder?

    • Dr_Frankenstein Dr_Frankenstein

      Hi Jim, you will find that hardlinks won’t work as you are going to need to have multiple paths mapped to your Sonarr container

      When you did your path mappings did you mount the /downloads directory into Sonarr as well? If not Sonarr cannot access the files that have downloaded for it to move to your final /video folder.

      If you have Discord might be worth reaching out so I can talk you through it.

  2. Andrew M Andrew M

    Interestingly I’m finding that Sonarr won’t move downloaded media once completed. Does it irrespective of using Transmission or Deluge as the torrent client.

    Got a brand new installation, and it’s still exhibiting the same behaviour…

    Privileges are correct, folder ownership is correct, yet works fine using Sonarr v2

    • Andrew Morris Andrew Morris

      worked it out, despite mapping /video/tv as /tv on the Sonarr container, it was expecting it to be mapped as /video/tv to /TV…

      now to retrofit on my production NAS….

  3. Bryan Bryan

    Really cannot thank you enough for these great tutorials!
    Everything working perfectly. Coffee coming!

  4. NewToSyn NewToSyn

    Having an issue where Sonarr can’t see and import the file once downloaded. In the logs it suggests the file either isn’t there or it’s a permissions issue. The User has read/write permissions and the Data folder is mapped (and works as I have imported media from it) so I am unsure what is going on. I know it’s possible to adjust download permissions in SABnzbd, is that maybe the solution?

    • NewToSyn NewToSyn

      Think I resolved it! Looks like file paths are case sensitive and SAB “Usenet” folder was mapped to lowercase “usenet”, so that’s where Sonarr was looking, but Sonarr could only see “Usenet”

      • Dr_Frankenstein Dr_Frankenstein

        Hey, yeah in Linux folders are all case-sensitive, so I always try to stick with lower case.

  5. arnaud arnaud

    Hi every one,

    my radarr docker setup is running perfectly fine but i’m stuck with sonarr
    when looking at the logs, the last line is :
    [Info] LanguageProfileService: Setting up default language profiles

    if anyone knows how to get out of this hole !

    (syno 6.2.3 if this is important)

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed. – writing Synology Docker Guides since 2016 – Join My Discord!