Nextcloud runs as user nobody and the permissions should be set for that user on that mount
That's way beyond the scope of this addon
Thanks for your reply and pointing this out.
Automatic updates is and should be disabled after this and whenever you want it updated it's actually not a big thing to fix manually.
It is mounted with proper UID but as RO indeed.
In my opinion though, doing chown -R here without a warning is both risky and pointless. And with a large archive mounted over a network it delays the startup with minutes and possibly hours. Finally, any existing ownership and group-access structure will be completely destroyed.
However, now everything is working properly and I'm very pleased with it. Kodi still as the main player and Plex for streaming services.
Maybe one thing, It would be nice and perhaps more "clean" to have a custom folder in addition to videos/tvshows/pictures. This as a mounted target may contain a mix of all those plus more.
Risky, perhaps, but pointless it is not. Chown on media files is a necessary evil here. This is a plugin that people expect to just work.
The default folders are the local folders on LE that are normally owned by root. But docker containers run as user nobody. We need to make them readable. I suspect most people using this plugin are hosting their media on a usb drive attached to LE. That's why we're not getting complaints about the chown.
The concern about the time it takes is valid. We can perhaps stat the top folder and chown only when necessary.
An alternative is doing a chmod -R go+r which would still cause issues with remote mounts.
What you did will work until the addon is updated for any reason, then it will be overwritten
Whatever the ownership is, plex needs to be able to read the files on there. Unlike libreelec, plex in this container runs as user nobody, not root
Docker containers stop when the primary process exits.
Try `docker run -it ubuntu bash` and you'll get bash running as the main process with terminal access.
But that's not really the way to build le. You're better off using a dockerfile with the dependencies and the le build steps in it
I have similiar issue, but I need to run container BEFORE kodi tries to start.
I installed MariaDB through docker
Docker service is already in system.d. If I would define "--restart unless-stopped" for container, it would be started automatically, but I dont know how to control startp sequence. And I need to have DB up before Kodi start, obviously, to be able interconnect Kodi and MariaDB.
I already tried /storage/.config/system.dCode
- Description=MySQL Container
- ExecStart=/bin/sh -c "exec sh /storage/mysql_start.sh"
- ExecStop=/bin/sh -c "exec sh /storage/mysql_stop.sh"
where mysql_start.sh is just docker start mysql but for some reason this service doesnt work...
Use the mariadb addon instead
No, you would install from usb/sd as if you're installing it on a brand new machine. That will repartition the drive with more space availabe for the boot partition
Also use a different port on the outside, other than 22
But really you should set up a vpn server so you vpn in first and then access anything on the lan as usual
Installation is the easy bit. I had that done in about 5 minutes.
Configuring it is another story. So far I've been trying to figure it out, on and off, for almost 2 days and I still can't even create a new database. All the online tutorials do not seem to be relevant to LibreElec. I just get a string of CLI errors, can't find the socket, etc, even from inside the docker container, when I try to follow a tutorial. Each new error leads me down a seeming endless mesh of interconnected rabbit holes, lol
To be fair, configuration is not unique to docker. Even if you installed mariadb from a package manager you would still have to configure it almost the same way.
Configuration via phpmyadmin or any other mysql client is exactly the same. Doing it via cli first requires exec'ing into the container. The rest is the same.
The socket error you mentioned in the other thread, I've never seen and should not happen. If you provide more details I can try and troubleshoot.
If you can't install it on your platform, I believe there is a docker compose docker you can use
If there is a choice to do, this is my point of view :
Docker is for a very specific usage, and deliver very large images size.
Guix IS a package manager that produce packages that can be installed without Guix.
Finally, if you need docker, why don't install it from Guix?
Docker is already included
Thank you for the hint. That did the trick - had to google a bit, how to mount a nsf shared folder, but I got it to worked now. Great Addon
Another quick hint, all the apps in our docker addons run as the user nobody (id 65534) and group user (99) because running as root is not recommended for many of them. So make sure that the mount points have permissions that allow access to that user
Another option would be to not define any restart options for the container and use a systemd service to manage it
I just installed Plex via the LE docker repo. I have access to the server and it looks like its running so far.
But I can't add any share media folders from my NAS. 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 disabled and enabled the Addon, restarted Kodi (using Libreelec 8.2.5. with RP2), but nothing helps. If i chance the mapping back to the standard "/storage/tvshows" (for example) Plex is starting again.
The NSF share is working fine, since I am using it for my Kodi library. I also tried SMB share but with the same issue.
May I miss something!?
Some more information. 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 tried to use the commnd "docker ps -a" to to see all images, but its completley blank. When I reset the settings to default the image show perfectly and Plex is starting.
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. So I can't see why Docker can't recognize the image after I changed the settings?
Here is my changed setting file:Code
- <setting id="E_VERSION" value="public" />
- <setting id="V_config" value="/storage/.kodi/userdata/addon_data/docker.linuxserver.plex" />
- <setting id="V_data_movies" value="nfs://192.168.178.100/Media/Movies/" />
- <setting id="V_data_tvshows" value="/storage/tvshows" />
- <setting id="V_transcode" value="/storage/downloads/plextemp" />
You can't use an nfs:// address as a location map, docker does not recognize that. You need to mount the nfs share in libreelec to a local path, and use that local path in addon settings