Posts by aptalca

    They contracted Baylibre to develop mainline Linux support which was topic of Linuxcon 2017/2018.

    I'm not sure if everything needed on the video side is already done.

    Afaik, libreelec is working closely with baylibre on that, but it is an ongoing effort. There are development builds for various arm devices including s905x with mainline kernel. Just not ready for primetime yet

    S905X is a SoC and the drivers are there. You don't sell SoCs these days without providing Linux drivers or giving access to specifications.

    So the main difference between those boxes is the remote control.

    The remote may be the major difference between boxes from different sellers/manufacturers, but the issue here is with the chipset manufacturers/designers, ie. Amlogic and the like.

    Afaik they only release drivers and software for a really old kernel and they only seem to care about android (I could be wrong, but that's my understanding of the situation)

    In docker, the containers by default are sandboxed from the host. So for a container to be able to access a file on the host, the file or the folder containing it has to be mapped in docker parameters.

    The addon provides two folder mappings, one for the /config folder and one for the /recordings folder, which is by default set to /storage/recordings so with the default settings, the /storage/recordings folder on le is accessible inside the container at the location /recordings

    Your m3u location would not be accessible inside the container unless you either move it to the /storage/recordings folder, or you change the path for the /recordings folder to cover the m3u location.

    I hope this is clear

    LibreELEC 9.0 on x86

    I tried to install Pi-Hole and it worked the 1st time (I was able to access the web ui).
    The I rebooted the machine and it didn't start. I tried to uninstall PiHole and Docker and reinstall them.

    No luck.

    What am I doing wrong ?

    Are you using the pihole addon or the docker commands?

    It could be a number of things. Your media may not be named in the style Plex likes it so it may be having issues identifying. Or you may have been having internet connectivity issues and requests may have been timing out, or you may have been getting throttled by the metadata provider.

    The one thing I can think of with regards to usb drives is that flash drives usually have pretty awful write speeds. Plus, plex libraries can grow to hundreds of thousands of files easily and to hundreds of gigabytes (especially if you turn on video preview thumbnails). I really wouldn't recommend hosting the Plex library on a flash drive.

    With that said, there are no issues with the Plex docker container. Many people use with very large libraries (on ssds mostly) and scans are fairly quick.

    I don't use nextcloud so I have no idea what that is. Ask on our discord or GitHub

    Did you read the answer and how it was solved in the next post?

    You cannot use nfs:// or smb:// locations as mount points with docker. You need to mount those smb locations on LE first and use those locations