kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

revert unrelated change

pull/7860/head
Medya Gh 2020-04-22 17:50:13 -07:00
parent 929dd7dd6e
commit a9f565bb27
2 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pkg/minikube/registry/drvs/hyperkit/hyperkit.go
View File

@ -96,7 +96,7 @@ func status() registry.State {
cmd := exec.CommandContext(ctx, path, "-v")
out, err := cmd.CombinedOutput()
if err != nil {
return registry.State{Installed: true, Error: fmt.Errorf("%s failed:\n%s", strings.Join(cmd.Args, " "), out), Fix: "Run 'brew install hyperkit'", Doc: docURL+"#old-hyperkit-version"}
return registry.State{Installed: true, Error: fmt.Errorf("%s failed:\n%s", strings.Join(cmd.Args, " "), out), Fix: "Run 'brew install hyperkit'", Doc: docURL}
}
// Split version from v0.YYYYMMDD-HH-xxxxxxx or 0.YYYYMMDD to YYYYMMDD

20
site/content/en/docs/drivers/hyperkit.md
View File

@ -23,8 +23,15 @@ minikube start supports additional hyperkit specific flags:
## Issues
### old hyperkit version
In start issues with hyperkit driver, upgrading hyperkit and ensuring the upgraded version is in the path, could solve the problem.
### Local DNS server conflict
If you are using `dnsmasq` and `minikube` fails, add `listen-address=192.168.64.1` to dnsmasq.conf.
If you are running other DNS servers, shut them off or specify an alternative bind address.
### hyperkit installation
The version of correct Hyperkit not being in the path could cause issues in starting minikube.
Try upgrading hyperkit and ensure the upgraded version is in the path, could solve the problem.
The latest version of hyperkit could be found [here](https://github.com/moby/hyperkit/releases).
You can check your current version by:
@ -43,11 +50,10 @@ To verify your hyperkit version please run;
hyperkit -v
```
### Local DNS server conflict
If you are using `dnsmasq` and `minikube` fails, add `listen-address=192.168.64.1` to dnsmasq.conf.
If you are running other DNS servers, shut them off or specify an alternative bind address.
alternatively you check the path of your hyperkit by:
```
which hyperkit
```
### Other