![]() ![]() 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. ![]()
0 Comments
Leave a Reply. |