Posts by Iridium

This *might* work

1) Create NEW folder to contain the executable
mkdir /storage/bin
2) Add this to $PATH

nano /storage/.profile

PATH=$HOME/bin:$PATH

3) Install docker from the LE addons (May not be needed)

4) Download Docker compose (All one line)

curl -L "https://github.com/docker/compose/releases/download/1.23.1/docker-compose-$(uname -s)-$(uname -m)" -o /storage/bin/docker-compose

5) Make it executable

chmod +x /storage/bin/docker-compose

6) Check to see it works

cd /storage/bin

./docker-compose --version

7) If it all works reboot.

---------------------------------------------------------------------------------------

If all else fails as @aptalca mentioned pull a docker container like this

If you can prove that it runs on LE then it *might* be considered.

I don't see why not - depends on what type of HW you are running and what you intend to do with it.

Are you trying to install on the same SSD as openELEC? as this might be the issue.

Depending on your version of OE you should be able to just upgrade to LE from your OE system.

LE is a read only system for a reason. There is no need for a package manager as nothing can be installed apart from addons.

If it doesn't work on 8.2.5, Milhouse or 8.90.007 then it has to be a configuration problem at your end.

Are you connecting on 2.4 or 5 GHz?

What are your wifi settings on the LE addon - screen print

also output of:

ls -al /storage/.cache

also URL output of:

dmesg | paste

Firstly use an official LE release (Like 8.90.007) and not a Milhouse (Which are test builds only).

Are you using dhcp or static IP? If static what are your settings?. (A screen print will do) If dhcp then try static.

And repeat the debug listings.

Apart from running some debug logs to see what the issue is, you can just copy the alpha (Current 007) file to /storage/.update and reboot.

Quote from graschbaten

Hi @all,

How can i upgrade the piHole Docker from diginc/pi-hole to pihole/pihole?

They are the same thing - just renamed. Here

At the moment the LE addon is using pihole V 3.3 to use V4 you'll need to disable the pihole LE addon.

Download the new container:

docker pull pihole/pihole:latest

Then create and run a new script

docker run -d \

   --name pihole \

   -p 53:53/tcp \

   -p 53:53/udp \

   -p 80:80 \

   -e DNS1=9.9.9.9 \

   -e DNS2=149.112.112.112 \

   -v /etc/localtime:/etc/localtime \

   -v /storage/.config/pihole/:/etc/pihole \

   -v /storage/.config/pihole/dnsmasq.d/:/etc/dnsmasq.d \

   -v /storage/.config/pihole/html/:/var/www/html/html/ \

   -h $(cat /etc/hostname) \

   -e ServerIP=$(ip route get 9.9.9.9 | awk '{ print $NF; exit }') \

   -e WEBPASSWORD=libreelec \

   --restart=unless-stopped \

   pihole/pihole:latest

That will get you running on 4.0. There may be issues as noted by @aptalca

Looks like a new build should be in tonight, so updating should get everything back to normal/

Can you try 007 Here or upgrade to see if you still have issues.

However, there are issues with the game addon in 8.90.xxx releases so that may be the issue.

Usually this is due to incorrect router configuration or wifi settings.

Also the output of:

ifconfig

and

cd /storage/.cache/connman/

Find the latest directory. Something like wifi_xxxxxxxxxxxxxxxxx

cd to that directory

Post the output of

more settings

It looks like the "Games addons" have yet to make it into the alpha builds (Broken!).

Hopefully this will be resolved in 008 or Beta 1.

I'm not sure but I know that certain issues are attributed to NOOBS. I would try a fresh install of just LE from Here

Yes I can understand your issue, but are YOU willing to implement, compile and support such an addition?

This sounds like a compatibility issue between Chorus, the IOS app and Leia. Neither are maintained by LE, so there is little we can do.

Best to wait until a final LE Beta or full release.

Whilst USBIP looks interesting, I'm not too sure how printer support would be useful for a Media Centre.

Maybe others can find a use for this addition.

Not without a full set of debug logs.

Try updating to 8.90.006 and see if the issue still exists.