Docker Installation on ARMv7 not working

English Forums Installation
1

Hi,

I wanted to run homegear/Docker on an Odroid SBC with latest archlinux OS to control my homematic devices with a CUL stick. Processor/Architecture is: Quad-Core Samsung Exynos - ARMv7 Processor rev 0 (v7l) and the board is equipped with 2GB of RAM.

So the problem I face is, that when trying to start the docker container with the stable or nightly image, a lot of errors occur, and this is because of lots of files missing inside (I compared to another docker installation on my old raspberry-3:

  • /etc/homegear.config
  • /var/lib/homegear.data
  • /usr/bin/homegear*

So my question: is ARMv7 no longer supported or what can be the root cause for the missing binaries and config templates? Maybe @sathya or other devs have an idea?

Thanks!

2

Hi @homedev ,

armhf packages are still there, there is a dependency problem with Debian Trixie though for armhf. It is solved now and new packages are being build.

In the meantime, the Docker images are now using Debian Bookworm again.

So it should work again now.

Cheers,

Sathya

1 Like
3

Hi @sathya,

thanks a lot for the fast response and fix.

I will try tomorrow and give feedback.

Meanwhile a second question: https://doc.homegear.eu/ gives me an 403 Forbidden error, no docs can be read online. Is this WiP or can it be fixed - that would be great!

Best regards,
homedev

4

Hi @sathya ,
now the armhf docker image is complete. First it did not come up properly, but after reducing to the minimum services it started on my armhf board with 2GB of RAM:

sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ enocean.conf
sudo sed -i -r ‘s/#[CUL]/[CUL]/’ homematicbidcos.conf
sudo sed -i -r ‘s/#id = My-CUL/id = My-CUL/’ homematicbidcos.conf
sudo sed -i -r ‘s/#default = true/default = true/’ homematicbidcos.conf
sudo sed -i -r ‘s/#deviceType = cul/deviceType = cul/’ homematicbidcos.conf
sudo sed -i -r ‘s/#device = /dev/ttyACM0/device = /dev/ttyUSB0/’ homematicbidcos.conf
sudo sed -i -r ‘s/#responseDelay = 95/responseDelay = 95/’ homematicbidcos.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ homematicwired.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ insteon.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ intertechno.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ knx.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ kodi.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ max.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ m-bus.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ miscellaneous.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ sonos.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ zigbee.conf
sudo sed -i -r ‘s/moduleEnabled = true/moduleEnabled = false/’ z-wave.conf

cd etc/
sudo sed -i -r ‘s/# runAsUser = homegear/runAsUser = homegear/’ main.conf
sudo sed -i -r ‘s/# runAsGroup = homegear/runAsGroup = homegear/’ main.conf
sudo sed -i -r ‘s/^enableUPnP = true/enableUPnP = false/’ main.conf
sudo sed -i -r ‘s/^enableNodeBlue = true/enableNodeBlue = false/’ main.conf
sudo sed -i -r ‘s/^ipcThreadCount = 100/ipcThreadCount = 10/’ main.conf
sudo sed -i -r ‘s/^ipcServerMaxConnections = 50/ipcServerMaxConnections = 20/’ main.conf

Another thing is, that after start there is a “find” process running for round about 3 minutes until homegear starts inside the container. Why does it take so long and what is it looking for?

5

Hi @homedev,

I also reduced the number of threads used in the default configuration now. It will be applied in the next version.

The find sets permissions on the Homegear directories and files, because otherwise, Homegear wouldn’t work correctly.

Cheers,

Sathya