Closed sdixonbigdog closed 6 years ago
Looks like localkube is crashing in your VM. Could you attach the output of minikube logs
as well?
That folder appears to be empty...what do I need to do to get those logs to be produced?
Oct 20 16:58:28 minikube localkube[8105]: I1020 16:58:28.963987 8105 interface.go:259] No valid IP found Oct 20 16:58:28 minikube localkube[8105]: apiserver: Exit with error: Unable to find suitable network address.error='Una ble to select an IP.'. Try to set the AdvertiseAddress directly or provide a valid BindAddress to fix this. Oct 20 16:58:29 minikube localkube[8105]: I1020 16:58:29.164369 8105 server.go:112] Version: v1.7.5 Oct 20 16:58:29 minikube localkube[8105]: F1020 16:58:29.164421 8105 plugins.go:72] Admission plugin "AlwaysAdmit" wa s registered twice Oct 20 16:58:29 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=255/n/a Oct 20 16:58:29 minikube systemd[1]: Failed to start Localkube. Oct 20 16:58:29 minikube systemd[1]: localkube.service: Unit entered failed state. Oct 20 16:58:29 minikube systemd[1]: localkube.service: Failed with result 'exit-code'.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten /remove-lifecycle stale
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details: Environment: Microsoft Azure Size: Standard D2s v3 (2 vcpus, 8 GB memory)
Minikube version (use
minikube version
): v0.22.3cat ~/.minikube/machines/minikube/config.json | grep DriverName
): hypervcat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
):echo ""; echo "ISO version"; grep -i ISO ~/.minikube/machines/minikube/config.json
What happened: PS C:\Windows\system32> minikube status minikube: Running cluster: Stopped kubectl: Correctly Configured: pointing to minikube-vm at fe80::215:5dff:fe00:40f
What you expected to happen: PS C:\Windows\system32> minikube status minikube: Running cluster: Running kubectl: Correctly Configured: pointing to minikube-vm at fe80::215:5dff:fe00:40f
How to reproduce it (as minimally and precisely as possible): Create VM in Azure (Windows 10 EE, size Standard D2s v3 (2 vcpus, 8 GB memory). Install Docker for Windows (v 17.09.0-ce), install minikube, install kubectl.
Run: minikube.exe start --kubernetes-version="v1.7.5" --vm-driver="hyperv" --memory=2048 --hyperv-virtual-switch="Primary Virtual Switch" --v=7 --alsologtostderr
Output of
minikube logs
(if applicable): Windows PowerShell Copyright (C) 2016 Microsoft Corporation. All rights reserved.Anything else do we need to know: