Scott Murray

Hey @vijayrkn - would you be able to review this PR please? Thanks!

@vijayrkn bump :)

> I have left one minor comment and once it is fixed, I will approve the change. Thanks for reviewing @vijayrkn! Made the string comparison change and confirmed that the...

Yep, sounds good to me!

Hmm, I wonder if this is due defaulting the container runtime (to docker) when it previously was set to blank. I'll dig into this soon and see if I can...

This.. is odd. I think i've found a bug with upstream. I see a similar error when I run ```bash minikube start --driver=docker --nodes=3 -p "laaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaarge" -v=8 --alsologtostderr ``` it...

Thanks for reporting this! Would you mind sharing the terraform snippet for ``` resource "minikube_cluster" "periscope" { ```

I think I've gotten to the root of the issue (both with the tf provider and the minikube CLI directly). This is primarily due to minikube being in an inconsistent...

Although one interesting idea is we _could_ set the IP [directly on the node](https://github.com/scott-the-programmer/terraform-provider-minikube/blob/a6708365e0f892bf1f1e2f1a50dff52baef3212f/minikube/resource_cluster.go#L294-L301). Minikube currently [infers the IP](https://github.com/kubernetes/minikube/blob/6ae435e7b20e602ee6650ffd512358f2a00c9482/pkg/minikube/machine/machine.go#L121) from the driver much later in the provisioning, however, I don't...

> Hey @scott-the-programmer , I have actually ran `minikube delete --profile=periscope` multiple times. I have also done `minikube delete --all --purge` before running the terraform scripts. Still gave me the...