2

I am getting the following error when running terraform init on my Macbook. Can someone please help?

Provider registry.terraform.io/hashicorp/template v2.2.0 does not have a package available for your current platform, darwin_arm64.

My terraform is version is 1.1.4.

Karishma Kohli
  • 21
  • 1
  • 2
  • Does this answer your question: https://stackoverflow.com/questions/66281882/how-can-i-get-terraform-init-to-run-on-my-apple-silicon-macbook-pro-for-the-go? – Marko E Jan 24 '22 at 09:38
  • Does this answer your question? [How can I get \`terraform init\` to run on my Apple Silicon Macbook Pro for the Google Provider?](https://stackoverflow.com/questions/66281882/how-can-i-get-terraform-init-to-run-on-my-apple-silicon-macbook-pro-for-the-go) – arvymetal Jan 13 '23 at 17:11

3 Answers3

5

The hashicorp/template plugin became obsolete (in favor of the built-in templatefile function) some time before Apple introduced its new Apple Silicon platform. The only releases available for that provider are those which were published before that platform existed.

To move forward on Apple Silicon hardware, you'll have two main options:

  • Ideally, plan to migrate away from the obsolete provider and use the built-in template function instead. That function is built in to Terraform itself, and so doesn't need any external provider to work. It is also more capable than the old template_file data source in that templatefile can accept template variables of any type, whereas template_file only supports strings.

  • If you are not yet ready to migrate away from that provider then you may instead prefer to use the darwin_amd64 version of Terraform under Rosetta 2 emulation. If you use a Terraform CLI release for darwin_amd64 then it will in turn install darwin_amd64 provider packages, and so you'll be able to use the final release v2.2.0 of the template provider.

    Terraform is not officially supported under Rosetta 2, so how well this will work will depend on how complete Apple's emulation layer is, but it can hopefully serve as a short-term workaround until you're ready to stop using this obsolete provider.

Martin Atkins
  • 62,420
  • 8
  • 120
  • 138
5

I solved it by using the tfenv package, which can build a specific Terraform version adapted to the platform architecture.

I ran the following to install a version that works under my M1 Macbook (version 1.3.3 in my case):

brew uninstall terraform
brew install tfenv
TFENV_ARCH=amd64 tfenv install 1.3.3
tfenv use 1.3.3
arvymetal
  • 2,787
  • 1
  • 30
  • 39
1

For me building "hashicorp/template" from the source was the solution. I was using terragrunt.

git clone https://github.com/hashicorp/terraform-provider-template.git
cd terraform-provider-template
go build

move the binary to terraform plugins directory. You can create the directory if the plugin's directory does not exist.

mv terraform-provider-template ~/.terraform.d/plugins/registry.terraform.io/hashicorp/template/2.2.0/darwin_arm64/terraform-provider-template

Set execution permission to the terraform-provider-template binary file.

chmod +x ~/.terraform.d/plugins/registry.terraform.io/hashicorp/template/2.2.0/darwin_arm64/terraform-provider-template

terraform init or terragrunt init from your project folder.

Isanka Wijerathne
  • 3,746
  • 3
  • 26
  • 34