Skip to content

Commit

Permalink
Add workaround for hyperkit and dnsmasq users
Browse files Browse the repository at this point in the history
  • Loading branch information
Daemeron authored and dlorenc committed Sep 3, 2018
1 parent 7e921b3 commit 9578f3f
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/drivers.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,10 @@ The hyperkit driver currently requires running as root to use the vmnet framewor

If you encountered errors like `Could not find hyperkit executable`, you might need to install [Docker for Mac](https://store.docker.com/editions/community/docker-ce-desktop-mac)

If you are using [dnsmasq](http://www.thekelleys.org.uk/dnsmasq/doc.html) in your setup and cluster creation fails (stuck at kube-dns initialization) you might need to add `listen-address=192.168.64.1` to `dnsmasq.conf`.

*Note: If `dnsmasq.conf` contains `listen-address=127.0.0.1` kubernetes discovers dns at 127.0.0.1:53 and tries to use it using bridge ip address, but dnsmasq replies only to reqests from 127.0.0.1*

#### xhyve driver

From https://github.com/zchee/docker-machine-driver-xhyve#install:
Expand Down

0 comments on commit 9578f3f

Please sign in to comment.