To install and use these Docker images, you'll need to keep the above in mind while following their documentation.
#SONARR UBUNTU DOWNLOAD#
Keep in mind that Radarr 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 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 Radarr users, both inside and outside Docker. If this advice is not followed, you may have to configure a Remote Path Mapping in the Radarr web UI (Settings › Download Clients). The best solution is to use a single, common volume Some also recommend paths for the download client container that are different from the Radarr container, like This causes slow moves and doesn't allow hard links because theyĪre considered two different file systems Both problems can be solved with well planned, consistent paths. The second is a performance issue and causes problems for seeding torrents. torrents/My.Movie.2018/, but in the Radarr container that might be at The first is a problem because the download client will report a download's path as There are two common problems with Docker volumes: Paths that differ between the Radarr and download client container and paths that prevent fast moves and hard links. Radarr v4 will convert the given directory on startup if a Radarr v0.2 or v3 database is found.
#SONARR UBUNTU WINDOWS#
Sonarr can be installed on Windows as Windows Service or system tray application.Volume to mount the data directory and supply that path to Radarr as parameter. Sonarr can be installed as system tray application or Windows Service. A system tray application is started after the user logs in and is visible as an icon on the taskbar system tray.Ī Windows Service runs even when the user is not logged in, but special care must be taken since Windows Services cannot access network drives (\\server\share or X:\ mapped drives) without special configuration steps.Īdditionally the Windows Service runs under the 'Local Service' account, by default this account does not have permissions to access your user's home directory unless permissions have been assigned manually. This is particularly relevant when using download clients that are configured to download to your home directory. It's therefore advisable to install Sonarr as a system tray application if the user can remain logged in. The option to do so is provided during the installer. Most docker containers use /config volume to mount the data directory and supply that path to Sonarr as parameter. Sonarr v3 will convert the given directory on startup if a Sonarr v2 database is found. It's advisable to make a backup of the v2 data first.
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 Most Docker images suggest paths like /tv and /downloads. This causes slow moves and doesn't allow hard links because theyĪre considered two different file systems inside the container.
0 kommentar(er)
