Skip to content
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

0.7.2 macos/arm m1 issue #99

Open
rsavage-nozominetworks opened this issue Jan 16, 2023 · 4 comments
Open

0.7.2 macos/arm m1 issue #99

rsavage-nozominetworks opened this issue Jan 16, 2023 · 4 comments

Comments

@rsavage-nozominetworks
Copy link

When using 0.7.2 on Linux/amd64 the 0.72 version of the provider works great. However, when using this version on an arm mac (m1), seeing the following error. Looks like the hash signature is wrong?

╷
│ Error: Failed to install provider
│
│ Error while installing carlpett/sops v0.7.2: the current package for registry.terraform.io/carlpett/sops 0.7.2
│ doesn't match any of the checksums previously recorded in the dependency lock file; for more information:
│ https://www.terraform.io/language/provider-checksum-verification
╵
@carlpett
Copy link
Owner

Hi @rsavage-nozominetworks,
Is it possible the lockfile was generated on a machine with another architecture? You can fetch missing platform hashes by calling terraform providers lock -platform darwin_arm64.

@rsavage-nozominetworks
Copy link
Author

@carlpett No, the lock file is not getting generated with another architecture. This issue only happens with this provider on macs with the ARM silicon. I've tried it on different clean mac (m1) and the issue is reproducible. Does not happen with Linux, and does not happen with version 0.7.1 on mac-m1-arm. I can download the binary of 0.7.2, but I still get the checksum error. I suspect there's a problem with the checksum.

@carlpett
Copy link
Owner

Very odd. From what I can tell, the checksum is the same in the SHA256SUMS file as the binary that was generated in the release build (43f218054ea3a72c9756bf989aeebb9d0f23b66fd08e9fb4ae75d4f921295e82). Do you have a way to tell what you're getting?

@bryan-rhm
Copy link

@rsavage-nozominetworks I tested on M1 and works great, can you try deleting your folder .terraform and terraform.lock.hcl and run the terraform init again ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants