From 47e230e0a39ecdf44899c95c8e8d7cc5909a76b8 Mon Sep 17 00:00:00 2001 From: LinuxServer-CI Date: Fri, 24 Apr 2020 09:46:35 -0400 Subject: [PATCH] Bot Updating Documentation --- images/docker-sonarr.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/images/docker-sonarr.md b/images/docker-sonarr.md index 04b0ce4bf6..0635229f26 100644 --- a/images/docker-sonarr.md +++ b/images/docker-sonarr.md @@ -133,8 +133,10 @@ In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as bel ## Application Setup Access the webui at `:8989`, for more information check out [Sonarr](https://sonarr.tv/). + Special Note: Following our current folder structure will result in an inability to hardlink from your downloads to your TV folder because they are on seperate volumes. To support hardlinking, simply ensure that the TV and downloads data are on a single volume. For example, if you have /mnt/storage/TV and /mnt/storage/downloads/completed/TV, you would want something like /mnt/storage:/media for your volume. Then you can hardlink from /media/downloads/completed to /media/TV. -Another item to keep in mind, is that within sonarr itself, you should then map your torrent client folder to your sonarr folder: Settings -> Download Client -> advanded -> remote path mappings. I input the host of my download client (matches the download client defined) remote path is /downloads/TV (relative to the internal container path) and local path is /media/downloads/completed/TV, assuming you have folders to seperate your downloaded data types. + +Another item to keep in mind, is that within sonarr itself, you should then map your torrent client folder to your sonarr folder: Settings -> Download Client -> advanced -> remote path mappings. I input the host of my download client (matches the download client defined) remote path is /downloads/TV (relative to the internal container path) and local path is /media/downloads/completed/TV, assuming you have folders to seperate your downloaded data types. ## Docker Mods