Closed mstruk closed 7 months ago
Thanks @mstruk - I will get this further investigated at our end.
Thanks @mstruk - I will get this further investigated at our end.
@rposts There are more details about the things I tried at #222.
Thanks @mstruk - I will get this further investigated at our end.
@mstruk could we use release binaries as is? This worked for me:
git clone -b 23.0.5 https://github.com/keycloak/keycloak
cd keycloak/container/
docker build . -t quay.io/keycloak/keycloak:23.0.5
docker run --rm -it quay.io/keycloak/keycloak:23.0.5 -V
Keycloak 23.0.5
JVM: 17.0.10 (Red Hat, Inc. OpenJDK 64-Bit Server VM 17.0.10+7-LTS)
OS: Linux 5.4.0-170-generic s390x
@rposts Sure, if that works for you. I didn't find Keycloak image builds for s390x
in quay.io so I assumed this still needs to be built manually for your purposes. If you find this solution to work, it's fine with me to do it this way.
@rposts I can't make the s390x testsuite build to work with the latest Keycloak, so I had to disable it. Only the basic build is performed now, without the testsuite.
The issue is building the latest Keycloak from source on s390x. It needs to build javascript libraries for which it uses nodejs + npm and some npm packages include binary executables / libraries which are not available for s390x.