![]() If it's running as a regular App, you can either set the internal volume path for Sonarr's container to match the "actual" path, or you can use a Remote path mapping (slightly more complicated) If Transmission is running on a different machine, like your NAS, you'll likely have to use a Remote path mapping anyways (unless you're able to match the paths to the share on your Mini as they are on the NAS, which I doubt) That way the paths match without us having to do anything special. You didn't specify how or where you were running Transmission, but if that's also running in Docker on the same machine as Sonarr, we highly recommend configuring equal volume paths for both Containers. This means that the path Transmission has to the files/download directory needs to be the same as Sonarr's path to the files. Sonarr gets the path to downloaded files directly from Transmission. It's not important exactly what it's called, as long as we follow the same structure) That way, Sonarr can access our downloaded files at /data/downloads and import them to /data/Sonarr/My Favourite Series Ideally we want to give access to the downloads and library through the same Docker Volume, so that we can utilize hardlinks (means that we can have access to the same file in two places, without using double the space, also makes imports quicker and less resource intensive) Something like /mnt/share/:/datawith one directory for downloads and one for your library inside the /mnt/share directory (this path is the path to where you can access the files/directories through Finder. So we need to specify to Docker that we want to give our container access to a /configvolume (where things like the configuration and database will live), the directory where downloads are placed by Transmission, and the directory where we want our Library to live (called root folder in Sonarr) Outside of that, the container can only access what we specify, like Volumes (folders/shares) Docker will give it CPU and RAM resources automatically, and will let it connect to the network through Docker's internal network, and your host machine's network connection. We can think of a Docker container as a Virtual Machine for applications.īecause of this separation, our Container only has access to what we give it. In other words, it's a method of giving applications an environment to run in that's standarised and (more importantly for your issue) separate and isolated from the rest of your host machine. Let's take it back to some Docker basics: Docker is a way to sandbox applications. Please contact the moderators of this subreddit if you have any questions or concerns. I am a bot, and this action was performed automatically. Once your question/problem is solved, please comment anywhere in the thread saying '!solved' to change the flair to solved. Those humans will likely ask you for the exact same thing this comment is asking. If you're still stuck you'll have useful debug or trace logs and screenshots to share with the humans who will arrive soon.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |