Posts by aptalca

    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

    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

    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.

    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

    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

    Glad to hear it installed.

    The avahi errors are harmless, it's because libreelec/coreelec already has avahi running and the one in the container complains, but the addon turns it off shortly after the container starts.

    I'm not sure what that framework error is, the line is cut off and I can't see. Hopefully that's also harmless.

    With regards to volume mappings, pay attention to the addon settings. There, you are mapping the container folders /data/movies and /data/tvshows to folders on the host. By default they are /storage/videos and /storage/tvshows. So if you place a file in /storage/videos on coreelec, inside the container (or in plex settings) it will show up under /data/movies.


    Yup, that's exactly the issue. I'll try and fix that at some point, but in all honesty, my priority is always libreelec. We don't officially support coreelec. Also none of our team members at linuxserver run coreelec so we can't easily test that either.

    In the short term, you can modify the following file and replace LIBREELEC_ARCH with COREELEC_ARCH and disable and reenable the addon and it should work (don't uninstall)

    1. /storage/.kodi/addons/docker.linuxserver.plex/bin/docker.linuxserver.plex

    keep in mind that if you ever uninstall and reinstall the addon, you'll have to edit that file again

    Hmm the error is docker reference format, which suggests that there is an issue with one of the parameters. Did you change any of the addon settings? If so, go back to default and try again.

    If not, it could be an issue with coreelec. I suspect the way I determine the arch is no longer working. They probably renamed it.

    Here's my logic to determine whether it's x86_64 or arm: "sed -e '/LIBREELEC_ARCH/ !d' -e 's/[^.]*\.\([^"]*\).*/\1/' /etc/os-release"

    If they renamed it to COREELEC_ARCH that would surely break it.

    Can you do "cat /etc/os-release" and post the output?


    I managed to download Plex image manually and run it through commands. Does this help? See attached.

    But still nothing under:

    That doesn't help. Please delete all instances of plex and reinstall the linuxserver addon. And then get the systemd logs

    The other commands need a container name, which I don't have. I posted log earlier. Unless you mean a different log?

    The service/container name is "docker.linuxserver.plex"

    "systemctl status docker.linuxserver.plex.service" will tell you the current status of the systemd service that is responsible for creating and starting the container

    "journalctl -u docker.linuxserver.plex.service" will show you the log

    Since you mentioned there is no running container on your system when the addon is enabled, there must have been an error with systemd. We need to see the log to troubleshoot that.

    I just installed the addon on a fresh test instance and it fired right up