-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Native support for Apple Silicon M1 chip #10645
Comments
Update: I got my M1 Mac working, and vault builds without needing to modify anything. This is actually kind of weird, given that darwin/arm64 doesn't appear in build.sh, but maybe it's not required? However,
And if I try to
Is node only used for install builds, not dev builds, or something like that? It seems to be the current bottleneck. |
One more note: |
Hi @ZevEisenberg , thanks so much for filing this! We will almost certainly support building for arm64 sometime in the future! |
@HridoyRoy will you also support docker images built for arm64 too? |
node 10 goes end of life in around 6 weeks so I think this is fairly urgent. I tried building with node 14 (the latest LTS) but on an M1 Mac it throws a nasty exception:
Reportedly this was fixed in node 15.x and hopefully nodejs/node#35986 eventually get backported to the LTS. Building with node 15 does get further, but then we hit an error inside ember:
I hope this saves someone some time debugging this. |
Workaround for vault plugin, tested as working. cloned the repo, checked out the tag, ran make build (with go installed and configured w/
|
@michaelarichard which tag did you checked out? I am trying to build
|
please make darwin arm64 a first-class citizen. as of today it is still a major hassle for almost all hashicorp products 😢 |
Hi folks, For Vault 1.8+ we'll be providing darwin/arm64 binaries. There's a known issue with enterprise 1.8 arm64 binaries (https://www.vaultproject.io/docs/upgrading/upgrade-to-1.8.0#known-issues). We will address it in 1.8.1, so I'm going to close this. |
Is your feature request related to a problem? Please describe.
I have a project that depends on vault, and I have to use my Terminal in Intel translation mode ("Rosetta 2") when building the project on an ARM Mac.
Describe the solution you'd like
vault should build natively on darwin/arm64 to support Macs with M1 chips in them.
Describe alternatives you've considered
N/A
Explain any additional use-cases
N/A
Additional context
I tried fiddling with build.sh on my Intel Mac to force building for darwin/arm64, but was getting errors like this when I run
make dev
:My M1 Mac isn't set up yet (still migrating files), so I haven't been able to test there yet.
The text was updated successfully, but these errors were encountered: