All my things are updated to LE12/aarch64 so not volunteering to test .. but there's nothing special about the AMLGX image; it's functionally the same as RPi4 and other SoCs like Allwinner.
Alright, when I have some time, I'll PR the addons so the arm32 devices will attempt to use the arm64 images, which will serve as a stopgap until LE12.
Thanks, yeah, previously the addons were pulling the "latest" tag, which lets docker automatically detect the arch (in your case it would detect it as arm32 and wouldn't find an image since we deprecated them).
I just need confirmation from someone with an rpi and LE 11 so we can make sure it's not specific to amlogic.
It means the kernel is 64 bit, but the OS is 32bit, which includes all the packages, services and processes, including the docker service (that's why I'm surprised the user reported a 64 bit container worked). I mean the container does use the host's kernel so a 64bit kernel would definitely be a requirement, but I would have guessed other docker service related activities would need 64 bit in the userspace as well. I wonder if it's one of those things where some containers work fine, but some don't.
We need some testing before I do a mass update of all the addons.
Display MoreI'm running several docker images on LE11 on aarch64 amlogic with 32bits userspace too.
I bypassed the error message and succeeded to run my linuxserver containers again.
Edit the /storage/.kodi/addons/docker.linuxserver.nginx/bin/docker.linuxserver.nginx file.
- remove the sleep infinitely line (or comment it out).
- force to use arm64v8-latest image.
- disable the addon automatic update on Kodi.
That is news to me. I always assumed trying to run a 64 bit container on 32 bit userspace would make docker complain about wrong arch.
Unfortunately I currently don't have a spare device to test this on. Can someone confirm it works (without issues) on an rpi as well, then I can update the addons to use the arm64 image?
You can create the addons via command line, if you don't want to go around modifying the addon files. Just use the docker cli command from the image readmes and use the "arm64v8-latest" tag.
Thanks
Do you mean the jellyfin docker addon?
If so, see here: LinuxServer.io docker addons and general docker info
Can you post the output of "docker info" ?
linux/arm/v8 indeed suggests 32bit
To clarify, I don't believe there is a way to disable/enable/restart addons in kodi/le from cli.
However, as others pointed out, the linuxserver docker addons use systemd so if what you're after is simple stop/start, you can do that via systemctl. But you won't be able to change addon settings in between.
The proper and the only supported way is through the gui.
You can't. The addon always pulls the latest version.
You create a container manually via docker run
I don't recommend running docker container apps as root. Some flat out don't work (anything with php for instance). It also creates a security liability especially for ones with exposed guis.
Linuxserver docker addons run as nobody:users (65534:100). If you're mounting an external drive (or a remote share), make sure to mount it as user 65534:100 and chown as needed and it will be fine. Libreelec runs as root so it will be able to access it anyway.
You set the paths in the addon settings. Keep in mind that the remote paths should already be mounted and you use the local mount point.
If you want to add multiple paths, you can add additional docker parameters in the addon settings as well
Alternatively, you can use our cloudflared mod with any linuxserver container.
If you use it with SWAG, you can reverse proxy anything through that, including the Kodi web server.
There is a docker container for it that works really well
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
