-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🚀 Feature: Arm64 Support #1316
Comments
@fdelucchijr good luck! |
Hi @fdelucchijr did you had a chance to take a look? Let me know if I can un-assign perhaps someone else would love to try this 🙏 |
@scopsy Sorry, I didn’t have enough time to change the build pipelines myself. As It would took me a lot of time to change it and debug for the whole monorepo (also, y don’t know much of the needs in the project for the Python and other non-node.js dependencies). My first option was to wait until nikolaik/docker-python-nodejs#38 was finally resolved to recheck all the builds (as I remember that image was the only non ARM compatible), or in case I get a long vacation get edit the pipelines with a more specific Dockerfile for Node&Python. If other person wanna take this issue more directly or with more time just assign him it. |
I've put in a PR for this here: #3309 |
Closed by PR 5139 |
🔖 Feature description
Arm64/aarch64 support for docker images.
🎤 Why is this feature needed ?
Cloud is moving to Arm64 compute (probably cost related), many projects are already preparing for this new arch.
An example of this is the Oracle Cloud Offer in Amphere A1 VM’s.
✌️ How do you aim to achieve this?
I’ve already downloaded the repo thinking about making a PR with all the changes, but as for now I see some problems (as for now only one, but if I see more with add it with an edit):
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: