Posts by excalibur

I think I found the solution with docker :

# Create "my-volume"
docker volume create --driver=local --opt type=ext4 --opt device=/dev/disk/by-uuid/d28c6d3a-461e-4d7d-8737-40e56e8f384a my-volume
# Run a container with it mounted to a path.
docker run -v my-volume:/my-volume --rm -it alpine sh

Can Docker volumes be mounted from a device instead of bind mounting a directory?

I'd like to setup a docker service (docker-compose) on a Linux host with a container mounting an entire [removable] physical hard drive as a docker volume. I…

serverfault.com

OS: LibreElec 11

My SSD drive with one ext4 partition is recognized as /dev/sda1 on boot and automatically mounted in /media/<label>.

Sometimes, small physical disconnections happen I think and the SSD is suddenly remapped as /dev/sdb1 or /dev/sdc1 etc...

This causes my docker volumes mapped in this SSD (through /media/<label>/path ) to raise error when trying to access them later :

# ls /data/movies
ls: reading directory '/data/movies': Input/output error

Even if disk is correctly remounted to /media/<label> and access to /media/<label> works on the host, I need to reboot to make my containers see the paths again.

How could I fix this problem ?

Can I force udevil to mount devices by-id or by-label or by-uuid to fix this ?

Can I force docker to mount volume through /dev/disk/by-id instead of /media/<label> ?

That's it.

I just changed this line:

DOCKERIMAGE="linuxserver/plex:arm64v8-latest"

and also removed :latest in the last line.

My device : Odroid C2 (amlogic aarch64)

I use nginx, radarr, sonarr, plex and prowlarr with arm64v8-latest tag since I upgraded from LE 9.2 to LE 11 this summer (3-june-2023).

With the fresh LE11 install, I had a different error message from docker when pulling latest, something like "impossible to find an image for your architecture".

I auto-update my containers every week. No problem in 4 months so far.

I'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.

Quote from PackElend

how did you installed docker-compose? Did you followed Docker compose on LE ? - General Support - LibreELEC Forum?

I followed this : https://djismgaming.wordpress.com/2019/09/17/doc…e-on-libreelec/

Ctrl + C

or kill the process.

you can use systemctl status docker.linuxserver.swag to see the output after a systemctl start docker.linuxserver.swag command.

I created services for my *arr softwares in the same linuxserver way.

So they are all added in the docker.linuxserver.updater list to be updated.

I also use docker compose files.

Yep, systemctl start docker.linuxserver.swag will run the script you found.

and systemctl stop docker.linuxserver.swag will run the other stop script.

It's all setup with https://github.com/linuxserver/li…er.swag.service

And because of StartLimitBurst=3 if you restart 3 times in a short moment, you'll have to run the reset-failed command to be able to start it again.

You can use systemctl :

systemctl start docker.linuxserver.swag

start

stop

restart

status

reload

reset-failed

...

Quote from chewitt

See https://test.libreelec.tv/11.0/Amlogic/odroid-c2/ for current LE11 test images. The loose plan is to resume support for older GXBB, GXL and GXM hardware with LE11.

Such a good news !!

I was desperate with my old Kodi 18.2 python 2 on my Odroid C2 because last years scrapers updated to brand new python3 versions. And I wondered when I'd have to unplug this not so old SBC.

Which LE11 image is best to test : nightly or beta ?

System : LibreElec 9.0.2 on Odroid C2 arm

I updated radarr to v3 and now all https requests fail because of a RemoteCertificateChainErrors from Mono.

Certificate validation for https://sentry.servarr.com/api/9/store/ failed. RemoteCertificateChainErrors

I heard about Mono being replaced with Net Core but I don't know what it is about. What can I do to have TLS requests work with mono again ?

PS: I also have a log saying :

Mono is not running with --debug switch

Thank you

edit: I disabled "check certificate" in radarr v3 settings and it's working now.

Quote from Bloodshot

Hi

I was running Medusa 0.4.6 which was meant to be the last version that would run on Python 2.7

I've just logged into the web interface and there was an update notification (19 new commits ) so thinking it was a bugfix as 0.4.6 was only relased a few days ago I updated.

It killed the Medusa web interface and probably lots of other stuff as it transpires that the new update was indeed for Python3 only.

I've reinstalled Medusa but I'm now stuck on 0.3.4 and it sees no updates.

So just a quick warning to anyone running Medusa,please don't update to todays 0.5.1 release

Display More

Strange.

I talked to Medusa devs on Discord a month ago and I told them it would be nice to avoid autoupdate to a python3-only version if python3 is not detected.

They said they would add a bypass for py2 users to avoid such a situation. It seems they didn't...

I think i'm gonna switch to docker version.

Il depends how you installed it.

I use docker and it is automatically updated every week.

Quote from DugieHowsa

Noticed the following message in Medusa after the latest update:

I realize that this will likely require an upgrade on the LibreELEC side, and that LE probably isn't going to Python3 until v10.

Any thoughts on how to proceed come October?

Quote from thoradia

Abstain from upgrading Medusa between October 1st 2020 and the release of LibreELEC 10

I think Medusa update will not be possible if python 2 is detected.

That's the least they (Medusa devs) can do.

up

For your information, this python script PlexTraktSync can sync the Plex library with Kodi library through a trakt.tv account.

It's for free accounts and works very well.

Of course, Kodi Trakt official addon is needed.

Thank you for your help.

But this is a manual address set up, meaning if prefix is changed by the provider it will not work anymore untill I re-change manually my address to fit the correct prefix.

Am I right ?