-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FailFast if hyperkit is not installed. #5478
Comments
I will work on this. /assign |
It seems that minikube outputs Suggestion message And...I'm wondering.
|
@govargo we have our own docker-machine-driver-hyperkit that wraps arround the hyperkit driver. It's confusing to users because they think we are downloading the hyperkit for them. I agree it's useless to download our driver for hyperkit if the hyperkit itself is not installed. We need to fail fast and provide them instruction to install or it even better if they have brew we could do it for them |
@govargo it's yours ! Will be happy to review the PR |
Thank you for your comment! |
@govargo one request, we just had an issue that having an older hyperkit driver, caused this issue #5594 it would be great that as part of this PR, on top of checking if hyperkit is installed, we check for the hyperkit version, and if there is an update available or if it is older than a specific verison, warn user about it or ask them if they let us upgrade it for them |
OK,I see. |
We do this now as of minikube v1.6, unless they specify --vm-driver=hyperkit, at which point we warn I believe. |
@tstromberg Thank you for sharing. I'll close the PR #5833 |
on a fresh macbook I had the following errors (not installed hyperkit)
minikube is trying to Retry to see if there would be an executable. while we should fail fast and tell user without must noise, to install hyperkit.
we need to detect after the driver-download that the hyperkit is not installed and exit with the links to documentation how to install it.
https://minikube.sigs.k8s.io/docs/start/macos/
or simply say
The text was updated successfully, but these errors were encountered: