![]() So I'm not sure what your tv, movies, books and music folders are meant to be. If Sonarr was only able to "see" files at /tv/whatever then it all breaks.Įdit: I think I understand your question now and yes, you'll have a downloads directory next to your media directory. This way when your download client downloads a file, it thinks it's putting that file in /data/downlods/somefolder and when it broadcats to sonarr "Hey! I've finished downloading a file, it's currently at /data/downlods/somefolder, sonarr can go look at /data/downlods/somefolderand find the same file. As long as /data is the same across all containers, you can point them to whatever subfolders you want and it should click together nicely. Then within each application, they'll be set up by default to pick up from places like /tv and /downloads - forget that, you need to change them so they're all pointing to /data/. Everything should be able to "see" the same root /data folder and they should all be mounted identically. You want /mnt/user/myshare/whatever to map to /data on all of your containers. So as an example, sonar comes with a default volume mount of /tv that it expects you to fill in - ignore that, or map it somewhere you don't care about. You need to map all of your respective docker containers to the exact same /data location. The problem is that for hardlinks and such to work, we need to make sure each container has the same world view or they're going to be looking for files in places that don't exist. ![]() That's the beauty of containers, they're utterly isolated unless you explicitly tell them otherwise. So you "map" /mnt/user/myshare/ to /data on your container - the container reads and writes to /data completely unaware that it's actually writing to /mnt/user/myshare/. Containers will never, ever see a path like /mnt/user/myshare/, instead you "map" that directory to a fake directory that your container thinks it's accessing. Even then it only "sees" what you tell it to see. ![]() I'm not sure I completely understand your question, but I'll try an answer and let me know if it makes any sense:Ĭontainers can't "see" the files on your system unless you explicitly tell it about them. For the operation of applications in the Guides, this shouldn't be of any impact. Unraid also gives you an explanation if you click on the "use cache" option in a share with all the available options you can choose from. storage: use cache=yes (contains all of my stuff that will be temporarily held on the cache and then moved to the array).download: prefer download cache pool (contains everything being downloaded).copy: prefer download cache pool (contains downloaded stuff that I want to copy to my libraries, like Anime I have renamed for further processing).That means that frequently WRITTEN files are not well suited to be on the array but frequently READ files or files that you want to store long-term are better to be stored on the Array.įrequently written files are your Appdata folder which contains all your docker container configuration files or the system folder which contains the docker image or virtual machine images. It also depends on what files your are dealing with because everything on your array (when it is protected by a parity) will have an impact on its write speed. If you say "use cache=prefer" data is written from the array to the cache and also kept on the cache. The thing about shares depends on where your files should end up for a temporary period of time or permanently.įor example, if you say "use cache=yes" on a share then files will be stored on the cache first and later, when the mover is invoked, the files are being moved to the array. However, that doesn't mean you cannot have your own organization, you will probably spend some more time getting to know Sonarr/Radarr etc in regard to this.įor example, I didn't know about the TRaSH Guides at all and still could get everything up and running, this took some time to learn but now I know what I need to look out for or would know where the issue might be because I have spend the time with the system. The guides are AFAIK consistent so if you set up your shares the way described then you can be sure that your Radarr and Sonarr instances will put the files in the directories you expect them to be in so that everything works. I think that the TRaSH Guides are good for people who are not that knowledgeable or want to spend a lot of time troubleshooting this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |