-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Fails to install node binary when running in docker on apple silicon #964
Comments
Yeah, it looks like we'll try to download the x64 binaries. We really only support darwin so that we can test this buildpack locally. Nobody on the team has an M1 yet, so this isn't a big priority, though I'd entertain a PR. It looks like the bug could be fixed by changing the architecture calculation here: heroku-buildpack-nodejs/cmd/resolve-version/main.go Lines 142 to 147 in 39e4b17
(It should return |
Returning |
This would be really awesome to support multiple platforms. In our use cases specifically M1 and AWS Graviton architectures. We use heroku buildpacks and can now deploy to AWS Graviton processors. If the buildpack was able to Or perhaps the simplest approach for now would be to set an environment variable like
Would this work? Any thoughts? @jmorrell @edmorley @joshwlewis 🤔 For those engineers who support Sustainable Engineering 🌞 and Green Software 🌳 this would be a big deal as this would allow engineers to deploy the same code on ARM, while boosting application performance, using less energy and reducing costs. A win-win for all 👏 |
Describe the bug
The buildpack fails while attempting to install node when running in docker on apple silicon.
The expected behaviour is that the binaries install correctly.
To Reproduce
Steps to reproduce the behavior:
On an apple silicon machine with docker desktop installed:
.txt
extensiondocker build . --platform=linux/amd64
Versions (please complete the following information):
Yarn 1.22.10
]Additional context
Running heroku:20 and the buildpack in docker to create heroku-like runtime environment for local dev.
.
The text was updated successfully, but these errors were encountered: