heroku-buildpack-nodejs icon indicating copy to clipboard operation
heroku-buildpack-nodejs copied to clipboard

Published 20 hours ago • verified publisher icon heroku

Fails to install node binary when running in docker on apple silicon

Open mmmmmrob opened this issue 3 years ago • 3 comments

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:

  1. Download the Dockerfile.txt
  2. Remove the .txt extension
  3. run docker build . --platform=linux/amd64
  4. See error fail.log

Versions (please complete the following information):

  • heroku-20
  • node 14.x
  • NPM or Yarn Version: [e.g. Yarn 1.22.10]
  • latest (https://github.com/heroku/heroku-buildpack-nodejs/archive/refs/tags/latest.zip)

Additional context Running heroku:20 and the buildpack in docker to create heroku-like runtime environment for local dev.

.

mmmmmrob avatar Nov 29 '21 11:11 mmmmmrob

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:

https://github.com/heroku/heroku-buildpack-nodejs/blob/39e4b172dab00c79bca77393d444a1d74f4c63d4/cmd/resolve-version/main.go#L142-L147

(It should return darwin-arm64 for M1 macs)

joshwlewis avatar Dec 14 '21 17:12 joshwlewis

Returning darwin-arm64 to the getPlatform() fn didn't solve this for me. Are there any other solutions?

jaygould avatar Jan 26 '22 10:01 jaygould

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 detect the platform and binary to install that would be incredible 😃

Or perhaps the simplest approach for now would be to set an environment variable like NODE_PLATFORM=linux-arm64 that would pull the node distribution for ARM v8 🚀

NODE_PLATFORM would then default to the existing platform binary. This would ensure backwards compatability.

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 👏

abarke avatar Nov 15 '22 11:11 abarke