There are two common problems with Docker volumes: Paths that differ between the Sonarr and download client container and paths that prevent fast moves and hard links.
The first is a problem because the download client will report a download's path as /torrents/My.Series.S01E01/
, but in the Sonarr container that might be at/downloads/My.Series.S01E01/
. The second is a performance issue and causes problems for seeding torrents. Both problems can be solved with well planned, consistent paths.
Most Docker images suggest paths like /tv
and /downloads
. This causes slow moves and doesn't allow hard links because theyare considered two different file systems inside the container. Some also recommend paths for the download client container that are different from the Sonarr container, like /torrents
.
The best solution is to use a single, common volume inside the containers, such as /data
.Your TV shows would be in /data/TV
, torrents in /data/downloads/torrents
and/or usenet downloads in /data/downloads/usenet
.
The Sonar Viewer has been designed with ease of use in mind - just select a sonar file from disk, and you are good to go. We have a short introduction video that can be viewed here, and more details (and a link to two week trial download) can be found on this page. Please note that the sonar viewer requires Windows 7 or later, and hardware.
If this advice is not followed, you may have to configure a Remote Path Mapping in the Sonarr web UI (Settings › Download Clients).
Permissions and ownership of files is one of the most common problems for Sonarr users, both inside and outside Docker. Most images have environment variables that can be used to overridethe default user, group and umask, you should decide this before setting up all of your containers.The recommendation is to use a common group for all related containers so that each container can use the shared group permissions to read and write files on the mounted volumes.
Keep in mind that Sonarr will need read and write to the download folders as well as the final folders.
For a more detailed explanation of these issues, see The Best Docker Setup and Docker Guide wiki article.