terraform-bundle crashed

[iceycake]

terraform-bundle on Terraform 0.10.1 when running within a golang:1.8.3 docker container. There was no issue with 0.10.0.

terrafor-bundle.hcl

terraform {
  # Version of Terraform to include in the bundle. An exact version number
  # is required.
  version = "0.10.1"
}

providers {
  archive = ["~> 0.1"]
  aws = ["~> 0.1"]
  docker = ["~> 0.1"]
  dns = ["~> 0.1"]
  external = ["~> 0.1"]
  fastly = ["~> 0.1"]
  github = ["~> 0.1"]
  gitlab = ["~> 0.1"]
  grafana = ["~> 0.1"]
  http = ["~> 0.1"]
  ignition = ["~> 0.1"]
  kubernetes = ["~> 0.1"]
  local = ["~> 0.1"]
  mysql = ["~> 0.1"]
  pagerduty = ["~> 0.1"]
  random = ["~> 0.1"]
  rundeck = ["~> 0.1"]
  spotinst = ["~> 0.1"]
  template = ["~> 0.1"]
  terraform = ["~> 0.1"]
  tls = ["~> 0.1"]
}

$ docker run --rm -it -v `pwd`:/src --entrypoint /bin/sh golang:1.8.3
$ cd /src
$ go get github.com/hashicorp/terraform/tools/terraform-bundle
$ terraform-bundle package -os=linux -arch=amd64 terraform-bundle.hcl
Fetching Terraform 0.10.1 core package...
Fetching provider "docker"...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x9198ac]

goroutine 1 [running]:
github.com/hashicorp/terraform/plugin/discovery.(*ProviderInstaller).Get(0xc420693d88, 0xc42020a868, 0x6, 0xc42020c080, 0x1, 0x1, 0x0, 0x0, 0x0, 0x0, ...)
	/go/src/github.com/hashicorp/terraform/plugin/discovery/get.go:122 +0x4ec
main.(*PackageCommand).Run(0xc42020a440, 0xc4200100c0, 0x3, 0x3, 0x0)
	/go/src/github.com/hashicorp/terraform/tools/terraform-bundle/package.go:99 +0x90f
github.com/hashicorp/terraform/vendor/github.com/mitchellh/cli.(*CLI).Run(0xc420228240, 0xc420206db0, 0xc420191f68, 0xc420212498)
	/go/src/github.com/hashicorp/terraform/vendor/github.com/mitchellh/cli/cli.go:242 +0x229
main.main()
	/go/src/github.com/hashicorp/terraform/tools/terraform-bundle/main.go:77 +0x2e0

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.