Decided to update the docker image for HomeBridge in iHost because it indicated there was an update (within iHost docker screen.) BEWARE: It pulled the 64 bit version of HomeBridge docker!
I do not know how to fix this! iHost needs the armv7 version of the docker. This should be automatic and iHost does not allow specifing the architecture manually. Can anyone help?
Everyone is switching to 64bit. I’m afraid that if it’s not worth installing an older version, it won’t work!!!
Yes, understand. But HomeBridge is still publishing armv7 (32 bit) versions but for some reason, iHost docker is pulling the 64 bit version.
If convenient, please go to the iHost local web page (http://ihost.local), navigate to Settings → System Log, click Download Log, and then send us the complete log file (if the file is large, you can upload it to a cloud drive and share the link).
Once we receive the information, we will promptly forward it to our technical team for investigation. Thank you for your cooperation!
link to log file
Hello, we have analyzed your logs. You can try reinstalling Homebridge. Before starting it, please stop the manually started rogerrichards/homebridge-armv7 container to avoid port conflicts. Then observe whether it starts successfully. If it still fails to start, please provide the iHost system logs and the Homebridge container logs (you can find the download button in the top-right corner of the Logs section of the container). Thank you for your patience and cooperation!
Thank you for the reply. Because HomeBridge is critical to my system, I had to discover how to install the proper armv7 docker image on my iHost. I had to install docker on my Mac and use AI to guide me on creating an armv7 only image on my personal docker hub account. Loading that into iHost allowed me to restore HomeBridge after the 64 bit image which iHost installed incorrectly. I sent you logs from after I performed this alternative image which may have confused your interpretation of my problem. I can not tell from your message if you found the problem I discovered. I do not want to repeat installing homebridge from the main docker homebridge/homebridge image and crash my iHost homebridge.
I encourage you to try and reproduce the problem. Install Homebridge docker from default homebridge/homebridge on iHost and verify it is running correctly.
Hello, thank you for your detailed explanation and patience. We have analyzed the logs you provided and found that the HomeBridge image you pulled earlier was not a 64‑bit version, but the correct arm/v7 architecture. The startup failure you encountered was essentially caused by some anomalies during the upgrade process that prevented the container from completing its startup – it was not due to an architecture mismatch. In our internal tests, a fresh installation (pulling the image from the default source) runs successfully. Even if you temporarily stop the container you manually installed, it does not affect anything; and even if the newly installed HomeBridge is temporarily unavailable, it does not prevent you from restarting the container you already created.