The concern about the time it takes is valid. That's why we're not getting complaints about the chown. I suspect most people using this plugin are hosting their media on a usb drive attached to LE. But docker containers run as user nobody. The default folders are the local folders on LE that are normally owned by root. This is a plugin that people expect to just work. Chown on media files is a necessary evil here.
This as a mounted target may contain a mix of all those plus more. Maybe one thing, It would be nice and perhaps more "clean" to have a custom folder in addition to videos/tvshows/pictures. Kodi still as the main player and Plex for streaming services. However, now everything is working properly and I'm very pleased with it. Finally, any existing ownership and group-access structure will be completely destroyed.
And with a large archive mounted over a network it delays the startup with minutes and possibly hours. In my opinion though, doing chown -R here without a warning is both risky and pointless. It is mounted with proper UID but as RO indeed. Thanks for your reply and pointing this out.Īutomatic updates is and should be disabled after this and whenever you want it updated it's actually not a big thing to fix manually. Have tried to change this to "readonly, ro, read, notwriteable" etc but it doesn't change the startup behaviour of plex. storage/.kodi/addons//resources/settings.xml
Especially not if there are applications doing recursive chown's on everything. This is a big problem for me as it's a remote RO mounted location where RW is not an option. └─1476 chown -R nobody:users /storage/tvshows /storage/videos /storage/downloads/plextemp /storage/pictures It seems the plex addon requires writable access as it tries to take ownership of all files at startup for some reason.ĬGroup: /system.slice/ So I can't see why Docker can't recognize the image after I changed the settings? I don't think I did anything wrong with the mapping since I am using the tree folder structure inside Kodi to point to the right direction. When I reset the settings to default the image show perfectly and Plex is starting. I tried to use the commnd "docker ps -a" to to see all images, but its completley blank. When I edit the settings file to map to my shared network folder, it looks like the whole image isn't even recognized by Docker. I also tried SMB share but with the same issue. The NSF share is working fine, since I am using it for my Kodi library. If i chance the mapping back to the standard "/storage/tvshows" (for example) Plex is starting again. I disabled and enabled the Addon, restarted Kodi (using Libreelec 8.2.5. I tried to Map the NSF Share in the settings, as you described, but when I do this I can't access Plex anymore (it just wont't start). I have access to the server and it looks like its running so far.īut I can't add any share media folders from my NAS. I just installed Plex via the LE docker repo.