noobmil.blogg.se

Install sonarr using putty
Install sonarr using putty




  1. #INSTALL SONARR USING PUTTY PLUS#
  2. #INSTALL SONARR USING PUTTY DOWNLOAD#

If i manually put in the longer path starting in /volume1, Sonarr still can’t see it. Although the downloads are in /volume1/Docker/SabNZBD/config/Downloads/complete/tv the path in Sab setting shows /config/Downloads/. However, it looks like i will need to change the default base folder in SabNZBD. ie /volume1/media/downloads, /volume1/media/tv, etc, etc, and then just have a single /volume1/media = /media mapping and have everything configured to save/read under /media Think about creating a /volume1/media path on your host and then moving everything under that.

#INSTALL SONARR USING PUTTY DOWNLOAD#

Note - if you dont want to use a common root path you need to show the mapping for the download client so we can confirm there is a mapping in common - or failing that you created a remote path mapping in sonarr to account for the discrepancy it also makes finding issues with the containers much easier as everything is all under one common path it makes it easer to confirm that all your containers can see and have the same access to the /media pathĭoing it that way also means hard linking will work and it wont have to copy. Your download client saves to /media/downloads/sab/complete, sonarr has a root path of /media/tv, plex could use /media/tv as well.

#INSTALL SONARR USING PUTTY PLUS#

Realistically you have too many irrelevant volume mappings considering theyre all under the same parent host path - plus doing it that way means hard links cant work and it can only copy. What path is your download client setup to save completed files to? however, acter installing docker and sonarr (and radarr and Sabnzbd) those containers where automatically created without the Docker loacal user or group, and seems to run perfectly except for the who renaming and moving thing.Īnyone got any suggestions or see any errors?Īre you sure that path is correct? it looks like its saving into /config/Downloads/. it looks like they usually create a new local user and group while documenting the PUID and PGID, then create containhers through putty using the PUID and PGID. Now i’m not sure if any of this is acctually what you guys mean by path exsistance and permissions, so i was also hoping someone that has messed around with Asustor’s OS (ADM) and maybe even portainer is here on this forum and is able to… “Translate” some things that pertain to other nas OS that most poeple use.Įdit: Also, when looking at setup guides for sonarr with docker. I have also gone to the folder that the completed files are stored and giving every group permission to read/write in it and sub folders as well as the destination folder that i want sonarr to move the file to after it renames by just going to the folder, right clicking it, selecting properties, and selecting the “permissions” tab.

install sonarr using putty

In portainer i am able to look at the container for sonarr and change the owner to administrator, which i assume corresponds to the user list on my NAS.

install sonarr using putty install sonarr using putty

I use docker to run sonarr and use portainer to manage it with a web GUI (i also have putty and can SSH in but i have used it yet).

install sonarr using putty

SABNZBD is also installed on the NAS and so is the “complete” that do downloader puts the completed download in. I am able to navigate to downloaded file.






Install sonarr using putty