Do you mean the jellyfin docker addon?
If so, see here: LinuxServer.io docker addons and general docker info
Posts by aptalca
-
-
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.
Zero Trust Hosting and Reverse Proxy via Cloudflare, SWAG and AutheliaZero Trust Hosting and Reverse Proxy via Cloudflare, SWAG and Autheliawww.linuxserver.io -
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
-
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.
-
Display More
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
)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.
