From 321bf32014921f5d31cbcff94eae3c46f0910c64 Mon Sep 17 00:00:00 2001 From: Medya Gh Date: Wed, 22 Apr 2020 17:57:45 -0700 Subject: [PATCH] nit --- site/content/en/docs/drivers/hyperkit.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/site/content/en/docs/drivers/hyperkit.md b/site/content/en/docs/drivers/hyperkit.md index 19386ebc02..2fee8cee8b 100644 --- a/site/content/en/docs/drivers/hyperkit.md +++ b/site/content/en/docs/drivers/hyperkit.md @@ -29,11 +29,11 @@ If you are using `dnsmasq` and `minikube` fails, add `listen-address=192.168.64. If you are running other DNS servers, shut them off or specify an alternative bind address. -### hyperkit installation +### Hyperkit upgrade version 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. +Try upgrading Hyperkit and ensure the upgraded version is in the path. -The latest version of hyperkit could be found [here](https://github.com/moby/hyperkit/releases). +The latest version of Hyperkit could be found [here](https://github.com/moby/hyperkit/releases). You can check your current version by: @@ -46,16 +46,18 @@ To upgrade try: brew upgrade hyperkit ``` -To verify your hyperkit version please run; +To verify your hyperkit version please run: ``` hyperkit -v ``` -if the version didn't change to the latest version [here](https://github.com/moby/hyperkit/releases), you check if there is an existing hyperkit in the path: +if the version didn't change to the latest version [here](https://github.com/moby/hyperkit/releases), you can check if there is an existing hyperkit in the path. ``` which hyperkit ``` +alternatively you might want to install the latest version of docker-desktop. + ### Other * [Full list of open 'hyperkit' driver issues](https://github.com/kubernetes/minikube/labels/co%2Fhyperkit)