Posts by aptalca

Docker addon?

Was it a first run? Did you already go through the wizard?

It was a bug that has since been fixed

It's detailed here: https://info.linuxserver.io/issues/2022-08-29-custom-files/

The logs should tell you what's going on in your case. It was never supposed to be breaking the containers but unfortunately a bug was shipped with the baseimage for a few days, which has since been fixed. But any image built during those few days contains the bug until a rebuild.

Docker containers contain their own OS and environment and dependencies and all inside the container. It doesn't need to match the host OS. Kernel is the main thing shared between the container and the host.

172.x.x.x address is the docker network IP. You need to use your LibreELEC device's lan IP to access it

As a docker container, by default it is sandboxed. Anything the container should have access to, should be defined in the docker arguments. The addon only allows access to the config folder for saving persistent data and the music folder for access to media.

For that to work, the Bluetooth device likely needs to be mapped into the container. I've never attempted such a feat so I'm not sure if it's even possible.

There is no such thing as install when it comes to docker. It runs in a container. So you create a container and start it. That's it.

"docker create . . ." creates a container

"docker start . . ." starts a container

"docker run . . ." is the combination of docker create and start.

We don't publish LibreELEC add-ons for all of our images. There isn't an add-on for Firefox at the moment.

You can manage it via ssh and the cli command posted above.

Quote from brainwash

Hi,

I want to install Nextcloud on my Raspberry Pi 4 running LibreELEC. I followed the steps mentioned by Iridium in this post:

These steps worked just fine. But what is the next step?

I tried to connect to the Nextcloud by entering the IP of the Raspberry Pi with :443 at the end on my PC, but the connection fails. I know the IP is correct and with SFTP I can access the Raspberry Pi.

Do I have to manually start the Nextcloud or what else do I need to do?

(I have never worked with docker or LinuxServer.io before, so there might be an obvious solution to this )

Display More

Check the log via "journalctl -u docker.linuxserver.nextcloud" and it should tell you what's going on with the creation and start of the container.

A potential issue could be that port 443 is already taken so the container can't be started with that mapping. If that's the case, go into addon settings and change the port to something else that's not in use.

Quote from darav

Hi there,

If I'm allowed to pick up an old thread, I'm also stuck on this issue. I am very new to docker and can't find a way to use portainer. Here is the log:

Code

-- Journal begins at Wed 2022-01-26 06:55:27 WET. --
Jan 26 10:44:25 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:29 LibreELEC sh[59756]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:29 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:29 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:44:39 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 1.
Jan 26 10:44:39 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:44:39 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:42 LibreELEC sh[59809]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:42 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:42 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:44:52 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 2.
Jan 26 10:44:52 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:44:52 LibreELEC systemd[1]: Started docker.linuxserver.portainer container.
Jan 26 10:44:54 LibreELEC sh[59865]: docker: Error response from daemon: network lsio not found.
Jan 26 10:44:55 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Main process exited, code=exited, status=125/n/a
Jan 26 10:44:55 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Scheduled restart job, restart counter is at 3.
Jan 26 10:45:05 LibreELEC systemd[1]: Stopped docker.linuxserver.portainer container.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Start request repeated too quickly.
Jan 26 10:45:05 LibreELEC systemd[1]: docker.linuxserver.portainer.service: Failed with result 'exit-code'.
Jan 26 10:45:05 LibreELEC systemd[1]: Failed to start docker.linuxserver.portainer container.

Display More

I have no idea what the lsio network is...

lsio is the custom docker network set up by the updater addon, which is a dependency for all the docker addons in the linuxserver repo.

No idea why it says it doesn't exist. Try disabling and re-enabling the updater addon and check its log

I just realized the mention of watchtower above. So I should clarify my previous post. The updater addon that is referenced in the thread title doesn't auto recreate containers. So it's fine.

Watchtower however is often used to auto recreate containers based on image updates and that is indeed a bad idea. Never recreate containers when not paying attention.

Quote from elonesna

Automatic image update for docker containers is a very bad idea:

• there are containers that may have incompatibilities with others and whose update must be executed in a certain order, and even stop some while updating another (example: my wireguard server must start after pihole)
• updating a docker image can lead to an interruption of the streaming service (vpn, tv, video, ...)
• updating a docker image always creates a risky situation that should not be left to an automatic timer

It doesn't auto recreate containers. It only updates the image so none of those concerns are applicable here.

Updater only automatically deletes orphaned images, such as the ones that lost their tag because a newer image was downloaded for that tag. It doesn't auto delete non orphaned images even if they are not attached to a container.

libreelec-addon-repo/docker.linuxserver.updater at master · linuxserver/libreelec-addon-repo

Contribute to linuxserver/libreelec-addon-repo development by creating an account on GitHub.

github.com

The prune button in the addon settings however does remove all images not attached to a container, but that is a manual operation, not automated.

libreelec-addon-repo/settings.xml at master · linuxserver/libreelec-addon-repo

Contribute to linuxserver/libreelec-addon-repo development by creating an account on GitHub.

github.com

In other words, updater's cron operation uses "docker image prune -f" whereas the manual button uses "docker image prune -af" with the "a" being the critical flag.

Did you use Portainer? If so you probably didn't set the cap-adds correctly

Docker addons update when you reboot or do a disable/re-enable of the addon

172.x.x.x is a docker network IP. What you need to do is map the ports you need, so they can be addressed at the 192.x.x.x ip, which is the host (libreelec) ip

Our mariadb addon is set to start before Kodi

libreelec-addon-repo/docker.linuxserver.mariadb.service at master · linuxserver/libreelec-addon-repo · GitHub

Yes, the addons are compatible with LE 10

You don't have to install the repo from zip, it's included as an option in the LE repo. Just install the linuxserver repo from the LE repo first, and then go to linuxserver repo and you can install the docker wrapper addons.

If it's not working after install, check the journalctl logs via "journalctl -u docker.linuxserver.portainer.service" or the systemd status via "systemctl status docker.linuxserver.portainer.service" in terminal