Posts by aptalca

    Iridium - that seems so weird since he is not asking for support on the addons, or compatibility with those addons. Also really hard to enforce he can uninstall/disable and repost the the log and then re-enable/install them. At the very end there is no difference we did not change anything, just made it harder to interact with people.

    We can never rule out the possibility that one of those banned addons could be causing the issues as long as they are in there. A lot of those addons are very intrusive.

    If they temporarily uninstall those addons and post a log, we rule out that possibility.

    VPN might be advised for illegal content (which is not endorsed here), other than that there's really no reason to use it.

    I have to disagree. In the US, congress allowed ISPs to sell all user data for profit.

    I have my entire internet connection go through a vpn because I simply don't trust my ISP with my internet traffic data.

    My vpn provider on the other hand claims they keep no data or logs, and their claims have been tested in courts multiple times where they were subpoenaed to hand over data on specific users and the only data they had was that the said user was a paying subscriber, nothing else. Therefore I trust them.

    Images are read only. But you create a container from the image, which is rw, and ephemeral. Any changes you make are inside the container. Once you destroy the container, your changes are lost.

    You can copy your files out of there via "docker cp" before you destroy it

    Why don't you use the docker addon?

    LE on VMs already work as long as the gpu is passed through correctly.

    The problem is the virtual graphics drivers. Only the VMware virtual graphics driver is supported in the ova.

    But passthrough graphics work. I ran LE that way via kvm for years

    So, what is the suggested route now to install pi-hole: add-on or container?


    Addon is easier to set up, it still works, but is on an older version.

    Setting it up manually will get you the latest version, but may not work on some arm boxes out of the box and require some manual steps to fix it.

    I would suggest trying the manual method first and if you have issues, use the addon.

    Please don't take my question as criticism, thank you for the hard work.

    I am fine with getting it manually, (mind you, I did that and it seemed to grab the latest version and it works fine)

    Not at all. I just wanted to clarify that it was a deliberate decision to hold it back, and that we didn't abandon it ;)

    I didn't update the addon version for a couple of reasons.

    1. The latest version image simply didn't work on a lot of arm boxes.

    2. They changed how a lot of the settings are input, leading to any web gui settings changes reverting back every time the container is restarted

    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?