-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ARM builds #473
Comments
Sure, though I would have to think how to do it exactly :) If you'd have some other projects which implement this, please provide a link, could be easier by getting inspired by them :) |
I'm trying to run this project on a M1 Mac (ARM64) and I'm unable to connect to the queue. I received this error from AWS Java SDK:
In the docker logs I see only this and nothing else: Can I assume that this is because the lack of support for ARM64 on this project? If not any clue of what can be wrong? |
@avaz yes, that's probably the cause. If you hava java though, you can try running it in embedded mode, by adding the elasticmq dependency and starting the server in-tests. |
@adamw could you please get into more details how to do it? |
@olegakbarov You should add the following dependency in the test scope: https://mvnrepository.com/artifact/org.elasticmq/elasticmq-server_2.13/1.1.0 Then you should be able to start the server:
As described here: https://github.com/softwaremill/elasticmq#starting-an-embedded-elasticmq-server-with-an-sqs-interface Regarding ARM builds - PRs welcome :) |
@adamw thanks for the reply. Just to let you and everyone know what worked for me. I switched to the java native docker image ( Also recently I had stumbled on issue 123 and I had to the |
@avaz, I can see |
@adamw, would elasticmq-native get an arm image using the same codebase? |
I'll reopen until this is done :) |
I followed these steps, but the container hangs without logs in docker
|
@olegakbarov, after following your steps I run that image with command
There's probably something wrong with Dockerfile. I tried to build and run image generated from Dockerfile generated by |
After merging above PR and releasing new version - the ARM image for elasticmq-native will be available in Docker Hub. |
You can check out Docker Hub - the ARM image for elasticmq-native is available. |
I gave it a try but it doesn't work for me:
I can run the parent image, so it looks like something is wrong in the build process:
The non-native version works. And the native version works on amd64. |
@elruwen Could you run |
I saw that you run it via sbt, I am not familiar with building docker images like that. It looks like you are using somewhere build instead of buildx, because I can run the parent image on my ARM machine. |
You are right we are using sbt-native-packager to build Graal native image. Unfortunately native packager pull docker image for host arch that's why we end up with ARM compatible docker image and AMD compatible Graal native image. I have opened issue sbt/sbt-native-packager#1443 to get some more information regarding this topic. |
@adamw, it seems like there's darwin aarch64 support over at https://github.com/graalvm/graalvm-ce-dev-builds/releases now, could m1 arm native elasticmq-native images be a thing with it? |
Currently, ElasticMQ builds and works fine when using a Dockerfile on an ARM64 systems. Would it be possible for SoftwareMill to add the architecture to their Docker Hub releases?
The text was updated successfully, but these errors were encountered: