Closed mooreds closed 2 years ago
Currently, AdoptOpenJDK version 14 only supports Intel x64:
https://adoptopenjdk.net/releases.html?variant=openjdk14&jvmVariant=hotspot
Similarly, Oracle OpenJDK version 14 also only support x64:
We also cannot upgrade to OpenJDK 17 until we replace Nashorn. OpenJDK 17 will be the first JDK that supports the M1 chip, so perhaps we can get this upgrade done in October or November after the final release is done.
I'm receiving Java-related core dumps running the Fusion Auth docker container on an M1 MacBook.
Other than waiting for Fusion Auth to upgrade Java, what are my options for running it locally? Has anyone solved this or rebuilt the images for ARM?
Nvm, answered my own question by finding this: https://github.com/FusionAuth/fusionauth-containers#community-contributed-docker-images
jerryhopper's image is working for me!
Bumping this up.
With more and more new MacBook Pro's with M1 Pro/Max chips this becomes a problem for local development. Multi-arch images are not for enthusiasts anymore but for daily use. None of the engineers I know can run official FA images on new MBP's now (high CPU load, constantly stuck, high memory usage).
The jerryhopper's multi-arch image work great (kudos to him), but they are not "official" and have some release delay (only a day or two but still).
Think it's the time to adopt multi-arch.
Should work now... try out the tag :1.32.1_multi_test_2
https://hub.docker.com/r/fusionauth/fusionauth-app/tags
The next full release will begin building multi-arch! Including the Docker image that will run well on M1!
Thanks to @jerryhopper and all those that have helped contribute to the multi-arch support!!
Looks like there's GA support for the m1 chip with Docker.
https://docs.docker.com/docker-for-mac/apple-silicon/
We should test our image on this hardware (it should work, but there may be issues with mysql as mentioned in the above link).
It looks like openjdk runs fine on m1: https://doesitarm.com/app/openjdk/
Related
https://github.com/FusionAuth/fusionauth-issues/issues/1227