-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Integrate aarch64 into the building /release process #125
Comments
It seems like circli has arm support now: https://circleci.com/build-environments/arm/ |
What was the reason again that we keep circle around for only the release builds? Anyhow, not that setting up a self hosted runner for it on our build machine should be too difficult https://circleci.com/docs/2.0/runner-overview/ |
Unfortunately we can't run self-hosted runners on Circle CI. About why use Circle CI only for release builds is merely a matter of balancing the workload. |
84codes provides a range of multi-arch images They also have multi-arch packages for most linux distros |
Hi, I'm having some issues using 84codes crystal base images (because they have arm64 versions). Edit: For get that comment, the 84codes images entrypoint is different from the crystal base image. I've fixed the issue on my end. |
I settled on using alpine's crystal binaries, and have had no issues whatsoever (having also had some different issues with the 84codes images). Our Dockerfile looks like this, but you could simplify (and remove static build dependencies) if you don't care about having a separate build container, or use
|
Right now aarc64 tasks are run by CI, but they aren't really part of the build process.
(WIP)
The text was updated successfully, but these errors were encountered: