Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add workaround for dnsmasq and hyperkit users to drivers readme #3003

Merged
merged 3 commits into from
Sep 3, 2018
Merged

Add workaround for dnsmasq and hyperkit users to drivers readme #3003

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
21bfb62
Update macOS requirements
Daemeron Jul 21, 2018
2779619
Revert "Update macOS requirements"
Daemeron Aug 8, 2018
56e2db6
Add workaround for hyperkit and dnsmasq users
Daemeron Aug 8, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/drivers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,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