Manager 1.29.0 requires x86-64-v3 (UBI 10) — can you publish an x86-64-v2 image?

Manager UI
1

I am deploying Central + Edge on a small home server (Debian 13, Intel Pentium Silver N6005). That CPU has SSE4.2 but no AVX2, so it is x86-64-v2 only.

docker compose build of a manager image based on openremote/manager:1.29.0 fails with:

Fatal glibc error: CPU does not support x86-64-v3

Hub layers show 1.29.0 (and 1.28.0-core) on ubi10-minimal / ubi10/openjdk-21-runtime. UBI 10’s glibc refuses to start Java on this machine. Mosquitto and Zigbee2MQTT are fine.

Would you consider publishing manager (and Keycloak, if it is also UBI 10) for x86-64-v2, for example ubi9/openjdk-21-runtime? If the supported answer is “rebase the published image onto UBI 9 yourself”, that is useful to have in the docs as well.

I can rebuild from source; I would rather stay on the official tags if a v2 image exists or is planned.

2

Hi!

There is indeed no support for x86-64-v2 because of the base ubi10 image we’re using.
We’re looking into changing it for broader and better OS support, but it’s a lower priority for us.
Do you have any recommendations? Feel free to open an issue and/or pull request if you’d like.