Remove "Ignoring --vm-driver" warning #4998
Labels
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Related to #4855 and #4614
This warning is noisy and is always doing the wrong thing. It's raised in two scenarios:
1. User has an existing non-virtualbox VM and runs
minikube start
- sees warning.The user has not specified a --vm-driver here. We should quietly do what the user wants and resume their existing VM.
2. User has specified an existing VM, and runs
minikube start --vm-driver=xxx
The user has explicitly specified a VM driver. We should error and exit, rather than ignoring their request.
Implementation wise, the most obvious way to do this is change the default driver to
auto
. If they have an existing config, the automatic default is to use that driver. If not, we can stick withvirtualbox
and build toward "best available".The text was updated successfully, but these errors were encountered: