(/mnt/user/"YOUR-DOWNLOAD-SHARE-NAME")_ (/downloads) (/mnt/user/"YOUR-MEDIA-SHARE-NAME")_ (/media) Usually the container-paths are always set up as /"name-of-path." Now your container is like its own light weight OS so it does'nt share the same pathing as your host system Your config path is the appdata, so you create a share on your array (or better yet cache drive) named "whatever-you-want." This share is what you will use for host path. You can name your shares whatever you want, the only important thing is that the host paths are linked to to the docker paths with the correct information.Ī standard template for Radarr has your ports, media path, download path, config, and backup path. Your issue is that your missing a foundational understanding on how docker containers work. I will watch it in a bit and report back! *Edit: Automod linked the guides I am using, but I missed the video. Sorry if these have been answered, i am having a heck of a time. Additionally this guide has additional path mapping that spaceinvader1 does not mention?Īdditionally when I am looking at a template, Sonarr for example how do I differentiate which host path is the container path vs the host path? It seems the templates dont differentiate host vs container.
My concern is that this guide has the user create a "data" share as opposed to the "downloads" share spaceinvader1 suggests. I also located another guide that was create a week ago linked below. Are these still the go-to source for setting these containers up? I have watched spaceinaver1 videos but they seem to be from 2017-ish.
I ahve recently gotten my unraid server built and while I am beginning to explore I am getting conflicting information on how to get the Sonarr, Radarr, and Plex apps up and running.