Root Folder Not Mapping about lidarr

[Starbix]

I added a README to my dockerimages repo mentioning the UID/GID

[Starbix]

Haha no, I added it after your issue 😄

[danielunderwood]

This sounds a lot like a permissions issue. Docker accepting a UID/GID is dependent on the image being used and isn't really standardized. Are you seeing any errors in the logs? What does your Dockerfile look like?

Regardless of the issue, we should probably have some sort of feedback in the UI for an error.

[mccorkled]

https://pastebin.com/30aRXRdq

The entire top of the log is Lidarr looking for information from books that I have being snatched using a program called LazyLibrarian. Strange.

[danielunderwood]

Looks to be a permission issue from [v10.0.0.6791] System.UnauthorizedAccessException: Root folder path '/music/' is not writable by user 'nobody'. I don't think it should be a lidarr issue since we should have the same file access backend as sonarr and radarr.

You may want to run id in the terminal to see if the group and user IDs that you're giving are actually being used. I know there's an image out there from @Starbix, but I think that one uses environment variables UID and GID instead of PUID and GUID. If you aren't using that image, what are you using?

[mccorkled]

Changing those variables did the trick.

Thanks.

[mccorkled]

Must have missed it. Sorry guys.