Posts by aptalca

  • Domoticz Addon

    Docker containers are sandboxed. They only have access to things that you specify. Go into addon settings, turn on additional parameters and input "--device /dev/ttyACM0” and see if that works

  • Jeedom

    It looks like jeedom doesn't create its database automatically. It expects you to first create a database, and set up a user with access to it.

    So you need to use the mariadb docker addon to create it. But keep in mind that the db and user creation only happens during first start. Once the databases are set up, we no longer touch it, because we don't want to break your stuff. If you want to start over, you need to uninstall the mariadb addon and tell LE to remove user data as well. If you changed the data folder location in the addon settings, you'll need to manually delete that folder.

    Then you can install mariadb addon again. It will open the settings page, allowing you to enter the user and database details. Once that's set up, then you can enter that info into jeedom.

    In jeedom, use the libreelec lan ip as the mariadb address (localhost refers to inside the container).

  • You can help COVID-19 researchers with your LibreELEC box

    Hey guys, I just wanted to let you know that the LinuxServer team recently published two docker images to help scientists with COVID-19 research.

    The images are for Folding@home and BOINC, both of which distribute compute jobs to the machines of users from all over the world in order to crowd-source scientif1c research related computations. They are both currently prioritizing COVID-19 related research such as "predicting the atomic-scale structure of an important coronavirus prote1n (spike)" and "understanding how it binds to the ACE2 receptor required for viral entry into cells".

    We also just published docker addons so you can easily install them on your LibreELEC devices to help out.

    That's right, you can help out COVID-19 researchers by donating your unused cpu cycles.

    Here's a blog article we published about the images: COVID-19: How it's affected us, and how you can help

    Here's some LibreELEC specific info on the images:

    Both addons are avaliable through the Linuxserver.io repo. Go to addons, install from repository, Libreelec addons, Addon repository and install the Linuxserver.io repo.

    Then go to addons, install from repository, Linuxserver.io addons, services and you can find Boinc and Folding@home.

    When you install either addon, it will first download and unpack the docker images, which can take some time. Be patient. You can watch the logs via the following commands

    Code
    journalctl -u docker.linuxserver.boinc -f
journalctl -u docker.linuxserver.foldingathome -f

    Boinc: GitHub - linuxserver/docker-boinc

    Fairly heavy image, because the app has no webserver, instead we run guacamole to display the gui app in a browser. Once installed, you can access it at http://libreelecIP:8088

    Switch to Advanced view in the menu, because some settings windows aren't displayed properly in the simple view.

    Add the Rosetta@Home project for COVID-19 research.

    Works on x86_64, arm and aarch64. But not all projects support arm and aarch64

    Folding@home: GitHub - linuxserver/docker-foldingathome

    Lighter image, as it has its own webserver. Once up, you can visit its relatively simplistic webgui at http://libreelecIP:7396

    For more fine grained control, you can access it remotely from another machine that has FAHControl installed. The default port for that is 36330 and there is no password auth.

    Unfortunately, F@H is x86_64 only

    Now, get folding!! ;)

  • Docker container networking and LibreELEC iptables

    It's not an iptables issue, it's a docker thing. You're likely putting the containers in the default bridge network, which doesn't allow them to connect to each other via container name as dns host name.

    The link you provided uses docker compose, which by default creates a "user defined bridge" network, which allows containers to connect to each other via container name.

    What you should do is, create a user defined bridge network via "docker network create mynet"

    Then when you're creating the containers, select "mynet" as the main network.

    Here's a detailed explanation: Using Docker networks for better inter-container communication

  • Docker Jellyfin HW accelarated transcoding in Raspberry pi

    Just to provide an update here, we updated both jellyfin and emby addons in the linuxserver repo. They now both support omx hw transcode.

    Go into the addon settings and toggle openmax. When the container is recreated, necessary devices and drivers will be mapped in.

    One gotcha though, neither supports hw decode. They only do hw encode. According to jellyfin documentation, that is an upstream limitation: Hardware Acceleration | Documentation - Jellyfin Project

    I also tested v4l2 (everyone says it's the future). It is detected and used by both emby and jellyfin (again, only for encode) but unfortunately the image has a green filter over it. No idea why, so we didn't enable that in the addon yet. Let me know if you have any idea what causes it and/or how to fix it.

  • Plex Media Server on LibreELEC

    Quote from t1t0

    Hello new here,

    After scrolling down 7 pages of this, some a little bit older, i ask, whats the best way to install plex server on libreelec? Use dockers, install directly, apt-get does not work. Does plex server comes as a add-on or i have to add a repo?

    Libreelec has no package manager so no apt-get. However, there are scripts to install Plex natively (and update) on libreelec. Escalade posted links to them in the previous page.

    Another way of installing Plex is via docker image. There is an add-on in the repo for that. You first install the linuxserver repo from the libreelec repo, then you'll see various docker add-ons in there.

    Which way is best is arguable. I'd say whatever you're more comfortable with is the best way. Try and see.

  • LibreELEC, linuxserver/letsencrypt and fail2ban

    Quote from librero

    WIth the default action seems that isn't used. That it was missing I think was found when I tried:

    banaction = pf[actiontype=<allports>]

    Not sure if currently packet filter can even be enabled. So other more advanced custom filters using pf directly won't be possible either.

    From action.d/pf.conf:

    Code
    # we don't enable PF automatically; to enable run pfctl -e 
# or add `pf_enable="YES"` to /etc/rc.conf (tested on FreeBSD)

    Afaik pfctl is an openbsd tool. I doubt it's available on linux.

  • Linuxserver.io Nextcloud not updated?

    Quote from berniejonnie

    Back from a trip I see your message, I tested and it looks like the add-on updated to V.1.04

    But I open the configuration page and see the same crippled picture as before!

    Maybe a fresh install would do it, but this is not possible because the other linuxseerver.io addons require it and so can not be deactivated/deleted etc....

    Any idea ?

    In your userdata folder for the updater addon, there should be an empty settings.xml file. Delete that and restart the device. With the new version, that file won't be created anymore (which was the original issue where kodi leia somehow fails to read the addon's main settings file if there is a blank but properly formatted user xml in userdata)

  • Plex Media Server on LibreELEC

    Quote from enrydgl

    Ok but now I have another problem.

    I try to set in PMS HttpUI the my movie directory (external USB hdd on Raspberry /var/media/<mydiskname>/). But I don't found my device in list of directory in PMS configuration (UI).

    So, I change the configuration into "Plex (LinuxServer.io)" service. I change the directory Movies /var/media/<mydiskname>/movies/".

    Appears these notifications Dockers: Plex kill and Plex stop. So I restarted Plex LinuxServer.io service (appear notification Plex start).

    But now... UI PMS http://..... don't work! I don't understand!

    It's going to appear in the container (and in the Plex gui) as "/data/movies" as the addon settings page says.

    You really should read this: LinuxServer.io docker addons and general docker info

  • Plex Media Server on LibreELEC

    Quote from enrydgl

    Ok now I understand. I installed LinuxServer.io Addon on Libreelec. Into this Addon I install the services Plex.

    So now I have: Plex (LinuxServer.io), Docker and Docker image Updater AddOn.

    Now Plex Client work with LibreElec PMS...and URL: http://<iprasp>:32400/web work.

    Plex-update.sh and plex.service files where I must save them and used them?

    Thank you

    It's one or the other. What escalade is referring to is a whole another method of installing Plex.

    If you already set up the docker addon and Plex is working, you don't need to do anything else. It will automatically update when you reboot your box.