EHRbase doesn't build Docker image on aarch64

[jpwiedekopf]

Background

I am building a docker container for EHRbase from source on my MacBook with M1 (aarch64) processor. The new 0.23.0 version of EHRbase doesn't build as aarch64 natively, since Temurin/Adoptium 17 is not available in aarch64 (c.f. the JFrog repo for aarch64 vs. that for x86_64).

Enhancement

As long as Adoptium 17.x is not available for aarch64, a possible workaround would be using a different JDK, perhaps Azul Zulu.

Further information

I've created a variant of the Dockerfile for the current (2023-01-12) version of Azul Zulu. I've tested building with no build arg (i.e. TARGETPLATFORM = 'linux/arm64' successfully on my laptop, and have also successfully stood up EHRbase on a real Linux AMD64 machine. It doesn't work with targetplatform=linux/x64 or linux/amd64 on the MacBook, but I think that's okay. This is certainly a somewhat niche usecase, but developers must be happy too when running their local EHRbase during client development, and Rosetta is slooow. This wasn't an issue with older versions of EHRbase, I've been running 0.21.1 under arm64 for a while now. ;)

[ChillarAnand]

I just stumbled upon this issue. Any plans to add support for M1?

[sidharthramesh]

I’ve had a similar workaround as well.
Usually I build the jar on my machine and then copy it into a Java runtime base image which has arm64 support.

For some reason building the jar within an arm64 docker image made the server run slower for me (think we had this discussion in another issue #604)

Having native support for an arm64 image would be great for sure.