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. 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.
#SONARR REMOTE PATH TV#
Your TV shows would be in /data/TV, torrents in /data/downloads/torrents and/or usenet downloads in /data/downloads/usenet. If this advice is not followed, you may have to configure a Remote Path Mapping in the Sonarr web UI (Settings › Download Clients). 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. The 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.įor a more detailed explanation of these issues, see The Best Docker Setup and Docker Guide wiki article.
#SONARR REMOTE PATH INSTALL#
To install and use these Docker images, you'll need to keep the above in mind while following their documentation. There are many ways to manage Docker images and containers too, so installationĪnd maintenance of them will depend on the route you choose. Now that transmission is setup, we can move on to sonarr, and radarr. Linuxserver.io is one of the most prolific and popular Docker image maintainers.
#SONARR REMOTE PATH HOW TO#
Note: Sonarr and Radarr are essentially the same, so I will only demonstrate how to setup Sonarr and these steps can be repeated for Radarr. Note: With these steps select the test connection button each time you add an api to ensure that everything is working properly. They also maintain images for most of the popular download clients as well.
LinuxServer specifies a couple of default volumes such as /tv and /downloads. Our recommendation is to use a single /data volume, as mentioned above. Hotio doesn't specify any default volumes, besides /config. Images are automatically updated 2x in 1 hour if upstream changes are found. Read the instructions on how to install the image.Thank you, I got that, and that is indeed what each container has mapped. However, I've got a downloaded torrent sitting in /data/completed (so /content/completed and /downloads, respectively), but Sonarr is telling me that it can't find any video files to import. I actually had pretty much the same setup before utilizing your excellent tool (until I saw mediabox, I had put off a new install, and had actually been working off a cloned image of an earlier ubuntu hardware setup, so thank goodness for you.) How do you test a sonarr setup torrent# In my prior setup, I had DelugeVPN and Sonarr in separate docker images (but I didn't have them in stacks, so I was losing jackett connectivity in docker.) As I mentioned in my first post, in order to resolve a similar issue with downloads not being processed, I had to use Sonarr's mapping feature in the Download Client section, which resolved the problem.
0 kommentar(er)
