sonarr container doesn't see the contents of /home/

[goodpunk6]

i'd love to point sonarr to my ~/LDMS/pi/media folder but sonarr doesn't see the contents of /home/.

[GreenFrogSB]

Sonarr or any other container will only link your fost folder to what is declared in docker-compose.yml file

in example, if you edit docker-compose.yml file located under /LMDS and then navigate to sonarr declaration part, you will find section "volumes:" and inside:

  - ./media/tvshows:/tv
  - ./downloads:/download

It means that the Raspbian OS folder /home/pi/LMDS/media/tvshow will be seen by the sonarr container under /tv the same with /home/pi/LMDS/media/downloads and /download This is your link between Raspbian OS and Sonarr container - I try to explain this in the video about mounting an USB drive to LMDS.

I hope that helps.

On Mon, Oct 11, 2021 at 4:52 AM goodpunk6 @.***> wrote:

i'd love to point sonarr to my ~/LDMS/pi/media folder but sonarr doesn't see the contents of /home/.

[image: Screen Shot 2021-10-10 at 11 51 56 PM] https://user-images.githubusercontent.com/15090661/136730828-4fe95646-4f31-4542-ac3a-f0bab12f2767.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GreenFrogSB/LMDS/issues/25, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARFVEPS25QQUEUXMZKMUDFTUGJNQDANCNFSM5FXIOCCQ .

[goodpunk6]

I still have a problem where when I select /tv as a root folder under media management, it doesn't save. When I attempt to add a show, it says invalid path. /tv does appear as an option for me to use. Please advise.

/downloads, /config, and /tv all appear under system

radarr was able to add /movies without a problem

[goodpunk6]

How does one solve this one?

Unable to add root folder
Folder is not writable by user abc

[mlervaag]

I had a problem with /media/tvshows (which /tv is mapped to) being owned by root, and this caused the same issue for me.

I changed the permissions on the folder so that my user (pi) was the owner with this command: sudo chown -R pi:pi media/

I suspect that this is because the compose settings for radarr is specifying PUID and PGID as 0 instead of 1000. This means that when deploying the radarr container is might make the media folders as root.

[goodpunk6]

Sorry I spoke prematurely. It is not fixed.[image: chrome_7J42rGSNNw.png]

On Wed, Oct 20, 2021 at 9:08 AM M G @.***> wrote:

That fixed it! Thanks so much!!

On Wed, Oct 20, 2021 at 7:56 AM mlervaag @.***> wrote:

I had a problem with /media/tvshows (which /tv is mapped to) being owned by root, and this caused the same issue for me.

I changed the permissions on the folder so that the 'pi' user was the owner with the command: sudo chown -R pi:pi media/

I suspect that this is because the compose settings for radarr is specifying PUID and PGID as 0 instead of 1000. This means that when deploying the radarr container is might make the media folders as root.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GreenFrogSB/LMDS/issues/25#issuecomment-947593050, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADTEHZIIN2AJ4MIU3HP65D3UH2VAJANCNFSM5FXIOCCQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[goodpunk6]

would it make sense to run this inside of the container? sudo chown -R pi:pi media/

[goodpunk6]

I solved the problem. I didn't know that after changing the docker-compose file that you had to go into ./delpoy.sh and hit the option to update docker-compose. I set the volume to be the remote mount I originally wanted. All is well in the world.