Posts by aptalca

    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

    Hello I am trying to run domoticz on boot as a docker container, so I have the following "domoticz.service" file in /storage/.config/system.d

    After a reboot the domoticz container starts (I can see it running from "docker ps" command), but after some seconds it suddenly stops. If I enable the parameter "Restart" to "Allways" the docker container keeps starting and stopping in a loop.

    If I check the container logs with the command "docker logs domoticz", I get the following:

    If I run the ExecStart command manually it works perfectly. What is wrong?

    Thanks!

    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?

    Thanks!

    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

    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

    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.