Posts by aptalca

Docker containers stop when the primary process exits.

Try `docker run -it ubuntu bash` and you'll get bash running as the main process with terminal access.

But that's not really the way to build le. You're better off using a dockerfile with the dependencies and the le build steps in it

Quote from JimmySmith

I have similiar issue, but I need to run container BEFORE kodi tries to start.

I installed MariaDB through docker

Code

docker run -d p 3306:3306 --volume=/storage/mysql:/config -e TZ="CET-1CEST,M3.5.0,M10.5.0/3" -e MYSQL_ROOT_PASSWORD=xoxo -e=MYSQL_USER=xyxy -e=MYSQL_PASSWORD=xzxz --name mysql lsioarmhf/mariadb

Docker service is already in system.d. If I would define "--restart unless-stopped" for container, it would be started automatically, but I dont know how to control startp sequence. And I need to have DB up before Kodi start, obviously, to be able interconnect Kodi and MariaDB.

I already tried /storage/.config/system.d

Code

[Unit]
Description=MySQL Container
Requires=service.system.docker.service
After=service.system.docker.service
Before=kodi.target

[Service]
ExecStart=/bin/sh -c "exec sh /storage/mysql_start.sh"
ExecStop=/bin/sh -c "exec sh /storage/mysql_stop.sh"
TimeoutStartSec=60
TimeoutStopSec=60
Restart=always
RestartSec=10
StartLimitInterval=0

[Install]
WantedBy=kodi.target

Display More

where mysql_start.sh is just docker start mysql but for some reason this service doesnt work...

Use the mariadb addon instead

There is an openvpn-as docker image you can use: https://hub.docker.com/r/linuxserver/openvpn-as/

But it's x86_64 only as there is no arm or aarch64 package for openvpn-as

No, you would install from usb/sd as if you're installing it on a brand new machine. That will repartition the drive with more space availabe for the boot partition

Also use a different port on the outside, other than 22

But really you should set up a vpn server so you vpn in first and then access anything on the lan as usual

Quote from jimmygolitely

Installation is the easy bit. I had that done in about 5 minutes.

Configuring it is another story. So far I've been trying to figure it out, on and off, for almost 2 days and I still can't even create a new database. All the online tutorials do not seem to be relevant to LibreElec. I just get a string of CLI errors, can't find the socket, etc, even from inside the docker container, when I try to follow a tutorial. Each new error leads me down a seeming endless mesh of interconnected rabbit holes, lol

To be fair, configuration is not unique to docker. Even if you installed mariadb from a package manager you would still have to configure it almost the same way.

Configuration via phpmyadmin or any other mysql client is exactly the same. Doing it via cli first requires exec'ing into the container. The rest is the same.

The socket error you mentioned in the other thread, I've never seen and should not happen. If you provide more details I can try and troubleshoot.

If you can't install it on your platform, I believe there is a docker compose docker you can use

Quote from flavi1

If there is a choice to do, this is my point of view :

Docker is for a very specific usage, and deliver very large images size.

Guix IS a package manager that produce packages that can be installed without Guix.

Finally, if you need docker, why don't install it from Guix?

Docker is already included

Error moving /etc/lighttp/lighttpd.conf in fresh container on arm · Issue #308 · pi-hole/docker-pi-hole · GitHub

Two official options here: Emby for Kodi - Emby

One syncs with the internal database, the other lets you access your emby content through a plugin

For play state syncing, I use trakt.tv

Quote from sonic00

Thank you for the hint. That did the trick - had to google a bit, how to mount a nsf shared folder, but I got it to worked now. Great Addon

Another quick hint, all the apps in our docker addons run as the user nobody (id 65534) and group user (99) because running as root is not recommended for many of them. So make sure that the mount points have permissions that allow access to that user

Another option would be to not define any restart options for the container and use a systemd service to manage it

Quote from sonic00

Hey there,

I just installed Plex via the LE docker repo. I have access to the server and it looks like its running so far.

But I can't add any share media folders from my NAS. I tried to Map the NSF Share in the settings, as you described, but when I do this I can't access Plex anymore (it just wont't start). I disabled and enabled the Addon, restarted Kodi (using Libreelec 8.2.5. with RP2), but nothing helps. If i chance the mapping back to the standard "/storage/tvshows" (for example) Plex is starting again.

The NSF share is working fine, since I am using it for my Kodi library. I also tried SMB share but with the same issue.

May I miss something!?

edit:

Some more information. When I edit the settings file to map to my shared network folder, it looks like the whole image isn't even recognized by Docker.

I tried to use the commnd "docker ps -a" to to see all images, but its completley blank. When I reset the settings to default the image show perfectly and Plex is starting.

I don't think I did anything wrong with the mapping since I am using the tree folder structure inside Kodi to point to the right direction. So I can't see why Docker can't recognize the image after I changed the settings?

Here is my changed setting file:

Code

<settings>
    <setting id="E_VERSION" value="public" />
    <setting id="V_config" value="/storage/.kodi/userdata/addon_data/docker.linuxserver.plex" />
    <setting id="V_data_movies" value="nfs://192.168.178.100/Media/Movies/" />
    <setting id="V_data_tvshows" value="/storage/tvshows" />
    <setting id="V_transcode" value="/storage/downloads/plextemp" />
</settings>

Display More

You can't use an nfs:// address as a location map, docker does not recognize that. You need to mount the nfs share in libreelec to a local path, and use that local path in addon settings

Glad to hear it installed.

The avahi errors are harmless, it's because libreelec/coreelec already has avahi running and the one in the container complains, but the addon turns it off shortly after the container starts.

I'm not sure what that framework error is, the line is cut off and I can't see. Hopefully that's also harmless.

With regards to volume mappings, pay attention to the addon settings. There, you are mapping the container folders /data/movies and /data/tvshows to folders on the host. By default they are /storage/videos and /storage/tvshows. So if you place a file in /storage/videos on coreelec, inside the container (or in plex settings) it will show up under /data/movies.

Quote from Martynet

here

Yup, that's exactly the issue. I'll try and fix that at some point, but in all honesty, my priority is always libreelec. We don't officially support coreelec. Also none of our team members at linuxserver run coreelec so we can't easily test that either.

In the short term, you can modify the following file and replace LIBREELEC_ARCH with COREELEC_ARCH and disable and reenable the addon and it should work (don't uninstall)

/storage/.kodi/addons/docker.linuxserver.plex/bin/docker.linuxserver.plex

keep in mind that if you ever uninstall and reinstall the addon, you'll have to edit that file again

Hmm the error is docker reference format, which suggests that there is an issue with one of the parameters. Did you change any of the addon settings? If so, go back to default and try again.

If not, it could be an issue with coreelec. I suspect the way I determine the arch is no longer working. They probably renamed it.

Here's my logic to determine whether it's x86_64 or arm: "sed -e '/LIBREELEC_ARCH/ !d' -e 's/[^.]*\.\([^"]*\).*/\1/' /etc/os-release"

If they renamed it to COREELEC_ARCH that would surely break it.

Can you do "cat /etc/os-release" and post the output?

Thanks

Quote from Martynet

I managed to download Plex image manually and run it through commands. Does this help? See attached.

But still nothing under: 192.168.1.50:32400/web/

That doesn't help. Please delete all instances of plex and reinstall the linuxserver addon. And then get the systemd logs

Quote from Martynet

The other commands need a container name, which I don't have. I posted log earlier. Unless you mean a different log?

The service/container name is "docker.linuxserver.plex"

"systemctl status docker.linuxserver.plex.service" will tell you the current status of the systemd service that is responsible for creating and starting the container

"journalctl -u docker.linuxserver.plex.service" will show you the log

Since you mentioned there is no running container on your system when the addon is enabled, there must have been an error with systemd. We need to see the log to troubleshoot that.

I just installed the addon on a fresh test instance and it fired right up