Skip to content

Sonarr in Docker on a Synology NAS

Key Settings and FAQ

Now you have set up Sonarr there are some key settings you will need to set as these often catch new users out. I will add more as they come up.

Media Management / Root Folders (Settings>Media Management)

Sonarr refers to the place(s) you keep your TV shows as Root Folders. These are where Sonarr will ultimately move your series episodes to once they finish downloading.

AppRoot Folder

Download Clients (Settings > Download Clients>Remote Path Mappings)

While most of the settings on this page are self-explanatory something that has caught people out if the Remote Path Mappings setting. If you are hosting all your services on the same NAS do not add any settings here.

Pages: 1 2

Published inDockerSynology


  1. I’ve got a Sonarr v2 installation running per your old guides, using Transmission, Jackett, Radarr v3, Prowlarr (for Radarr), and it’s all working nicely until I migrate to Sonarr v3, when everything goes to hell, and I start getting the Import failures, even if I’ve manually copied the files into the folder.

    I’ve built a “virtual” DSM on VMware using the same version of DSM, etc, but clean, and the only difference is that my path on the new one is “/TV” vs “/TV Shows” on my physical Synology.

    I’m not entirely keen on renaming the root folder of my TV Shows share, as I’ve got around 150 TV Series I’d have to edit in Sonarr, but for the life of me can’t work out what’s going on…. Any ideas?

    • Dr_Frankenstein Dr_Frankenstein

      Hey, does Sonarr throw any specific errors at all? If you were to rename the underlying share (although you shouldn’t need to) Sonarr v3 allows you to bulk edit the root paths on all your shows.

      • In v3, I get “Downloaded – Unable to Import: check logs for details”, irrespective of copying the files in manually, or with a downloader handling it.

        In Debug I get zero logs relating to the show I’m trying to work on at the moment, in fact it’s trying to match it to a completely different series of shows altogether…

        In Trace logging, I get something similar to:


        however the files are already imported, it just won’t update the DB

        and throws out this:

        2022-06-21 20:37:36.6|Trace|Owin|SQLite error (5): database is locked in “PRAGMA cache_size=-10000”
        2022-06-21 20:37:36.6|Trace|Owin|

        2022-06-21 20:37:36.6|Trace|Owin|SQLite error (5): database is locked in “PRAGMA cache_size=-10000”
        2022-06-21 20:37:36.6|Trace|Owin|

        I’m loathe to migrate of v2, as it just works so well and reliably…. but this has my really stumped

        • Dr_Frankenstein Dr_Frankenstein

          It might be worth setting up v3 with a blank slate and fresh config folder and then importing the existing shows to it. You could stick the old version on a different port temporarily so you can match up your other settings. I suspect because of the length of time since v3 was launched its not a smooth upgrade if going over the top of existing settings. Reach out on Discord as will be easier to chat it through.

  2. candyman candyman

    Hi there. Thanks for this awesome guide. I have one issue left and that is updating the synology media index. For some reason newly added episodes won’t be visible in uPnP until I re-index on the synology manually. I have tried setting up the synology indexer notifcation in sonarr, but that errors out (assuming because sonarr probably cannot connect to the synology indexer?). So am I the only one who has this issue, or is there somekind of fix for it? The workaround would be to schedule media indexing every night or so, but if I can get something better to work than that would be great.

    • I moved away from uPnP to Plex, as I found uPnP becoming increasingly unreliable over the years…

    • Dr_Frankenstein Dr_Frankenstein

      Hey, unfortunately this is a known issue with the indexer, I remember reading that it doesn’t always pickup the new files automatically. You will need to create the manual task. The Sonarr script doesn’t work as the Docker container has no access to the underlying system.

      As Andrew mentioned below if you did move to Plex make sure you go the Docker route and not the one in the package center.

  3. 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.

  4. 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. – writing Synology Docker Guides since 2016 – Join My Discord!