kubernetes / minikube

Run Kubernetes locally
https://minikube.sigs.k8s.io/
Apache License 2.0
29.59k stars 4.9k forks source link

minikube not starting #3907

Closed kentcb closed 5 years ago

kentcb commented 5 years ago

I'm trying to get minikube working on Windows 10. It failed in a VM, so I decided to try directly on my machine and it fails in a different way.

I'm executing:

minikube start --vm-driver=hyperv --hyperv-virtual-switch="Primary Virtual Switch"

And I get this output:

o   minikube v0.35.0 on windows (amd64)
>   Creating hyperv VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
@   Downloading Minikube ISO ...
 184.42 MB / 184.42 MB [============================================] 100.00% 0s

And that's it. There's no further output and I see the terminal bouncing between powershell.exe and minikube.exe processes every second or so. Inside Hyper-V manager, I see:

image

However, if I connect to the minikube VM it just shows:

image

minikube status outputs nothing useful:

> minikube status
host:
kubelet:
apiserver:
kubectl:

Doing Get-NetAdapter | Format-List shows that the primary virtual switch is down:

Name                       : vEthernet (Primary Virtual Switch)
InterfaceDescription       : Hyper-V Virtual Ethernet Adapter #2
InterfaceIndex             : 24
MacAddress                 : F0-6E-0B-CF-75-DC
MediaType                  : 802.3
PhysicalMediaType          : Unspecified
InterfaceOperationalStatus : Down
AdminStatus                : Up
LinkSpeed(Gbps)            : 10
MediaConnectionState       : Disconnected
ConnectorPresent           : False
DriverInformation          : Driver Date 2006-06-21 Version 10.0.17763.1

The .minikube\logs directory is empty.

UPDATE: I noticed that I had accidentally included = between args and their values, so I deleted the VM, deleted my .minikube directory, and tried again with the command minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch". However, it behaves exactly the same way :(

kentcb commented 5 years ago

Turns out I had selected the wrong adapter for the virtual switch. I selected the WIFI one instead of Ethernet. After changing it over and resetting/re-starting, it worked.