minikube/site/content/en/docs/drivers/hyperkit.md

---
title: "hyperkit"
weight: 1
aliases:
    - /docs/reference/drivers/hyperkit
---

## Overview

[HyperKit](https://github.com/moby/hyperkit) is an open-source hypervisor for macOS hypervisor, optimized for lightweight virtual machines and container deployment.

{{% readfile file="/docs/drivers/includes/hyperkit_usage.inc" %}}

## Special features

minikube start supports additional hyperkit specific flags:

* **`--hyperkit-vpnkit-sock`**: Location of the VPNKit socket used for networking. If empty, disables Hyperkit VPNKitSock, if 'auto' uses Docker for Mac VPNKit connection, otherwise uses the specified VSock
* **`--hyperkit-vsock-ports`**: List of guest VSock ports that should be exposed as sockets on the host
* **`--nfs-share`**: Local folders to share with Guest via NFS mounts
* **`--nfs-shares-root`**: Where to root the NFS Shares (default "/nfsshares")
* **`--uuid`**: Provide VM UUID to restore MAC address

## 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.
The latest version of hyperkit could be found [here](https://github.com/moby/hyperkit/releases).

You can check your current version by:

```
hyperkit -v
```

To upgrade try:
```
brew upgrade hyperkit
```

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.

### Other

* [Full list of open 'hyperkit' driver issues](https://github.com/kubernetes/minikube/labels/co%2Fhyperkit)

## Troubleshooting

* Run `docker-machine-driver-hyperkit version` to make sure the version matches minikube
* Run `minikube start --alsologtostderr -v=7` to debug crashes