Specifying alternate CIDR value does not work to solve CIDR conflict

[dougpagani]

The exact command to reproduce the issue:
minikube start
minikube start --host-only-cidr 172.16.0.1/24
minikube start --host-only-cidr 10.0.0.0/24

The full output of the command that failed:

😄 minikube v1.3.1 on Darwin 10.13.6
💡 Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
🔄 Starting existing virtualbox VM for "minikube" ...
E0830 00:13:46.694973 17088 start.go:723] StartHost: start: Error setting up host only network on machine start: host-only cidr conflicts with the network address of a host interface

💣 Unable to start VM
❌ Error: [HOST_CIDR_CONFLICT] start: Error setting up host only network on machine start: host-only cidr conflicts with the network address of a host interface
💡 Suggestion: Specify an alternate --host-only-cidr value, such as 172.16.0.1/24
⁉️ Related issues:
▪ #3594

😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose

The output of the minikube logs command:

💣 command runner
❌ Error: [SSH_AUTH_FAILURE] getting ssh client for bootstrapper: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
💡 Suggestion: Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.
⁉️ Related issues:
▪ #3930

😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose

The operating system version:
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.13.6
BuildVersion: 17G7024

[dougpagani]

NVM, figured out a fix. I'll give some context as well to help googlers, if any run into a similar scenario. Minikube stopped working with the same setup I had once I turned my machine on & off.

It had nothing to do with the CIDR block after all. Minikube just couldn't talk to the VirtualBox at all once it spun it up. I didn't think I had a vpn running, but there was indeed a sneaky-daemon from OpenVPN. It was a launchctl job so I had to find the plist and unload it.

Also, once I fixed the routing after ripping out the vpn launchd job, I still got the same error until I killed the old failed vm (minikube destroy) and tried again. Then it worked as per normal.

One suggestion is that the help message for this issue should print the actual/underlying issue instead (as it appears in minikube logs), since the actual issue (it just can't ssh-in to talk to the new minikube-image-VM) gives less misleading diagnostic info.