-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Closed
Labels
cause/vm-networkingStartup failures due to VM networkingStartup failures due to VM networkingco/hyperkitHyperkit related issuesHyperkit related issueshelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.os/macospriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Description
Is this a BUG REPORT or FEATURE REQUEST?: Bug
Please provide the following details:
Environment:
Minikube version: 0.22.0
- OS: macOS 10.12.6
- VM Driver: hyperkit
- ISO version: minikube-v0.23.3.iso
- Install tools:
- Others:
What happened:
Cluster did not start:
$ minikube start --vm-driver hyperkit -v 10
Starting local Kubernetes v1.7.5 cluster...
Starting VM...
Found binary path at /usr/local/bin/docker-machine-driver-hyperkit
Launching plugin server for driver hyperkit
Plugin server listening at address 127.0.0.1:58797
() Calling .GetVersion
Using API Version 1
() Calling .SetConfigRaw
() Calling .GetMachineName
(minikube) Calling .GetState
(minikube) Calling .Start
(minikube) Generated UUID 23bf5b8b-93fe-11e7-b603-784f43517719
(minikube) Generated MAC 6a:c7:25:8a:7f:2b
(minikube) Starting with cmdline: loglevel=3 user=docker console=ttyS0 console=tty0 noembed nomodeset norestore waitusb=10 systemd.legacy_systemd_cgroup_controller=yes base host=minikube
E0907 11:56:39.075265 54829 start.go:143] Error starting host: Error starting stopped host: IP address never found in dhcp leases file Temporary Error: Could not find an IP address for 6a:c7:25:8a:7f:2b
Temporary Error: Could not find an IP address for 6a:c7:25:8a:7f:2b
[... snip a ton of these errors...]
What you expected to happen:
The cluster starts normally.
How to reproduce it (as minimally and precisely as possible):
See above command
Output of minikube logs
(if applicable):
Anything else do we need to know:
I built docker-machine-driver-hyperkit
myself, but got the minikube binary from the latest official release here on Github. If there's a more official place to get docker-machine-driver-hyperkit
, I'll try using that one.
joshuarubin, ehimemikan, jwandrews, tylerkilburn, skyllo and 4 more
Metadata
Metadata
Assignees
Labels
cause/vm-networkingStartup failures due to VM networkingStartup failures due to VM networkingco/hyperkitHyperkit related issuesHyperkit related issueshelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.os/macospriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.