Skip to content

Sonarr in Docker on a Synology NAS

UpdateDate
Added Docker Compose details
Added new folder mappings to ensure atomic moves and Hard-linking
03/05/2021
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
docker/sonarr/config
data/data


Network

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.

variableValue
PUIDThe UID you obtained in the user setup guide
PGIDThe GID you obtained in the user setup guide
TZYour timezone wikipedia.org/wiki/List_of_tz_database_time_zones


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

e.g 192.168.0.40: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"
services:
  Sonarr:
    image: linuxserver/sonarr:latest
    container_name: sonarr
    environment:
      - PUID=YOURPUID
      - PGID=YOURPGID
      - TZ=Europe/London
    volumes:
      - /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

40 Comments

  1. Followed the guide for Deluge and Sonarr, everything works fine up until the point of import. where it fails with the following message. Any suggestions as the dockerlimited account has access to these folders and can see them

    “DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr. Ensure the path exists and the user running Sonarr has the correct permissions to access this file/folder”

    • Dr_Frankenstein Dr_Frankenstein

      Hey is there a bit extra to the error where it includes the folder path? It usually means the mount point is incorrect in your container setup. Sonarr needs to be mounted as /data and /data meaning it will have access to all subfolders (double-check your PUID/PGID is the right way around)

    • Deepcore Deepcore

      Never Mind, managed to solve it. Looks like there was a previous install that was causing this issue. Deleted the config folder and it sorted itself. Thanks for this amazing guide.

  2. Nick Nick

    Love these guides. So helpful. Can I just recommend modifying the network section to instruct people on what to do if they intend to run multiple sonarr dockers. If this is desired, the container port should be left at the default, but the local needs to be different from the container port and also unique from any other ports set on other containers. So all sonarr apps would be 8989 for container port, and each container local port would need to be unique, 8990, 8991, for example. Thanks again.

    • Dr_Frankenstein Dr_Frankenstein

      Thanks Nick, I will keep this on my notes for when I do the DSM7.1 rewrites

Leave a Reply

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!