The default volumes are not optimal nor recommended. LinuxServer specifies a couple of optional default volumes such as /tv and /downloads. They also maintain images for most of the popular download clients as well.
Linuxserver.io is one of the most prolific and popular Docker image maintainers. Read the instructions on how to install the image. Images are automatically updated multiple times per hour if upstream changes are found. Hotio doesn't specify any default volumes, besides /config. There are many ways to manage Docker images and containers too, so installationĪnd maintenance of them will depend on the route you choose. To install and use these Docker images, you'll need to keep the above in mind while following their documentation. Keep in mind that Sonarr will need read and write to the download folders as well as the final folders.įor a more detailed explanation of these issues, see The Best Docker Setup and Docker Guide wiki article. 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. The default user, group and umask, you should decide this before setting up all of your containers. Most images have environment variables that can be used to override Permissions and ownership of files is one of the most common problems for Sonarr users, both inside and outside Docker. If this advice is not followed, you may have to configure a Remote Path Mapping in the Sonarr web UI (Settings › Download Clients). Your Series would be in /data/tv, torrents in /data/downloads/torrents and/or usenet downloads in /data/downloads/usenet. The best solution is to use a single, common volume inside the containers, Some also recommend paths for the download client container that are different from the Sonarr container, like /torrents. This causes slow moves and doesn't allow hard links because they are considered two different file systems inside Most Docker images suggest paths like /tv and /downloads. Both problems can be solved with well planned, consistent paths. The second is a performance issue and causes problems for seeding torrents. The first is a problem because the download client will report a download's path as /torrents/My.Show.S01E01/, but in the Sonarr container that might be at 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. Of course, it is always advisable to make a backup first. Sonarr v3 will convert the given directory on startup if a Sonarr v2 database is found.
Most docker containers use /config volume to mount the data directory and supply that path to Sonarr as parameter.
0 kommentar(er)
