localkube: panic: unable to read certificate-authority /var/lib/localkube/\var\lib\localkube\certs\ca.crt #1981

F21 · 2017-09-19T00:13:40Z

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Please provide the following details:

Environment:

Minikube version: minikube version: v0.22.2

OS: Windows 10 64-bit (Creators Update with latest updates)
VM Driver: VirtualBox
ISO version: v0.23.4
Install tools: n/a
Others: n/a

What happened:
Minikube provisioned the VM, but it does not work correctly.

What you expected to happen:
The Minikube cluster should work correctly.

How to reproduce it (as minimally and precisely as possible):

Downloaded minikube 0.22.2 and placed it in my PATH.
Deleted C:/users/user/.minikube and C:/users/user/.kube
Ran minikube start.
The VM provisions correctly.
Tried to get into the dashboard:

$ minikube dashboard
Could not find finalized endpoint being pointed to by kubernetes-dashboard: Error validating service: Error getting service kubernetes-dashboard: services "kubernetes-dashboard" not found

$ minikube dashboard
Could not find finalized endpoint being pointed to by kubernetes-dashboard: Error validating service: Error getting service kubernetes-dashboard: Get https://192.168.99.101:8443/api/v1/namespaces/kube-system/services/kubernetes-dashboard: dial tcp 192.168.99.101:8443: connectex: No connection could be made because the target machine actively refused it.

Docker in minikube showed no containers running at all:

$ minikube ssh "docker ps -a"
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

In addition, since my CWD is C:/users/user/Desktop, I see this folder created C:/users/user/Desktop/C_/users/user/.minikube.

Output of minikube logs (if applicable):
See attached file
logs.txt

Anything else do we need to know:

The text was updated successfully, but these errors were encountered:

IljaKroonen · 2017-09-19T11:18:23Z

I have the same problem using Hyper V

This is at the end of my logs

Sep 19 11:15:01 minikube localkube[4739]: kubelet is ready!
Sep 19 11:15:01 minikube localkube[4739]: Starting proxy...
Sep 19 11:15:01 minikube localkube[4739]: Waiting for proxy to be healthy...
Sep 19 11:15:01 minikube localkube[4739]: E0919 11:15:01.386986    4739 server.go:428] unable to register configz: register config "componentconfig" twice
Sep 19 11:15:01 minikube localkube[4739]: I0919 11:15:01.391530    4739 feature_gate.go:144] feature gates: map[]
Sep 19 11:15:01 minikube localkube[4739]: E0919 11:15:01.391578    4739 server.go:318] unable to register configz: register config "componentconfig" twice
Sep 19 11:15:01 minikube localkube[4739]: kubelet: Exit with error: failed to run Kubelet: invalid kubeconfig: invalid configuration: [unable to read client-cert /var/lib/localkube/\var\lib\localkube\certs\apiserver.crt for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\apiserver.crt: no such file or directory, unable to read client-key /var/lib/localkube/\var\lib\localkube\certs\apiserver.key for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\apiserver.key: no such file or directory, unable to read certificate-authority /var/lib/localkube/\var\lib\localkube\certs\ca.crt for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\ca.crt: no such file or directory]
Sep 19 11:15:01 minikube localkube[4739]: scheduler: Exit with error: unable to create kube client: unable to build config from flags: invalid configuration: [unable to read client-cert /var/lib/localkube/\var\lib\localkube\certs\apiserver.crt for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\apiserver.crt: no such file or directory, unable to read client-key /var/lib/localkube/\var\lib\localkube\certs\apiserver.key for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\apiserver.key: no such file or directory, unable to read certificate-authority /var/lib/localkube/\var\lib\localkube\certs\ca.crt for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\ca.crt: no such file or directory]
Sep 19 11:15:01 minikube localkube[4739]: I0919 11:15:01.404225    4739 controllermanager.go:108] Version: v1.7.5
Sep 19 11:15:01 minikube localkube[4739]: E0919 11:15:01.405060    4739 controllermanager.go:116] unable to register configz: register config "componentconfig" twice
Sep 19 11:15:01 minikube localkube[4739]: panic: invalid configuration: [unable to read client-cert /var/lib/localkube/\var\lib\localkube\certs\apiserver.crt for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\apiserver.crt: no such file or directory, unable to read client-key /var/lib/localkube/\var\lib\localkube\certs\apiserver.key for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\apiserver.key: no such file or directory, unable to read certificate-authority /var/lib/localkube/\var\lib\localkube\certs\ca.crt for minikube due to open /var/lib/localkube/\var\lib\localkube\certs\ca.crt: no such file or directory]
Sep 19 11:15:01 minikube localkube[4739]: goroutine 2559 [running]:
Sep 19 11:15:01 minikube localkube[4739]: k8s.io/minikube/pkg/localkube.StartProxyServer.func1(0x3f91c80, 0x0)
Sep 19 11:15:01 minikube localkube[4739]:         /go/src/k8s.io/minikube/pkg/localkube/proxy.go:67 +0xaf
Sep 19 11:15:01 minikube localkube[4739]: k8s.io/minikube/pkg/util.Until(0xc42027c5c0, 0x8e27240, 0xc42000e018, 0x49ed2b1, 0x5, 0xbebc200, 0xc420010d20)
Sep 19 11:15:01 minikube localkube[4739]:         /go/src/k8s.io/minikube/pkg/util/utils.go:64 +0x6f
Sep 19 11:15:01 minikube localkube[4739]: created by k8s.io/minikube/pkg/localkube.(*SimpleServer).Start
Sep 19 11:15:01 minikube localkube[4739]:         /go/src/k8s.io/minikube/pkg/localkube/server.go:64 +0x7e
Sep 19 11:15:01 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Sep 19 11:15:01 minikube systemd[1]: localkube.service: Unit entered failed state.
Sep 19 11:15:01 minikube systemd[1]: localkube.service: Failed with result 'exit-code'.

The certificate actually does exist

$ pwd
/var/lib/localkube/certs
$ ls
apiserver.crt  ca.crt  proxy-client-ca.crt  proxy-client.crt
apiserver.key  ca.key  proxy-client-ca.key  proxy-client.key
$

But obviousy it is in /var/lib/localkube/certs, not /var/lib/localkube/\var\lib\localkube\certs\

EricssonVNFCloud · 2017-09-19T18:10:01Z

is the fix provided in #1982 ready to use ? can I download the latest .exe and install it fresh

IljaKroonen · 2017-09-19T20:44:22Z

After looking at some URLs I found out how to download the new executable (1982 is the # of the MR)

https://storage.googleapis.com/minikube-builds/1982/minikube-windows-amd64.exe

EricssonVNFCloud · 2017-09-19T20:46:46Z

Thanks buddy !!! do you know whether we need to remove the old one before installing this new one ??

IljaKroonen · 2017-09-19T20:54:25Z

I just replaced the executable in my installed folder, ran minikube delete and minikube start, and everything worked

EricssonVNFCloud · 2017-09-19T21:13:42Z

I am still getting this error:

minikube config set WantKubectlDownloadMsg false

Could not find finalized endpoint being pointed to by kubernetes-dashboard: Error validating service: Error getting service kubernetes-dashboard: Get https://19
2.168.99.100:8443/api/v1/namespaces/kube-system/services/kubernetes-dashboard: dial tcp 192.168.99.100:8443: connectex: A connection attempt failed because the
connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

EricssonVNFCloud · 2017-09-19T21:14:43Z

ping works file though......

C:\Users\eagamil>ping 192.168.99.100

Pinging 192.168.99.100 with 32 bytes of data:
Reply from 192.168.99.100: bytes=32 time=2ms TTL=64
Reply from 192.168.99.100: bytes=32 time=1ms TTL=64
Reply from 192.168.99.100: bytes=32 time=1ms TTL=64
Reply from 192.168.99.100: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.99.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

EricssonVNFCloud · 2017-09-19T21:29:38Z

I am trying to run on Windows 7

richardjharding · 2017-09-20T07:58:55Z

I just tried the build on the link above 1982 and still can't get minikube running on hyperv - this the output I get

[stderr =====>] :
[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM minikub
e ).networkadapters[0]).ipaddresses[0]
[stdout =====>] : fd65:76f8:30e8:1:215:5dff:fe01:d417

[stderr =====>] :
[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM minikube
 ).state
[stdout =====>] : Running

[stderr =====>] :
setting hostname "minikube"
[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM minikube
 ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM minikub
e ).networkadapters[0]).ipaddresses[0]
[stdout =====>] : fd65:76f8:30e8:1:215:5dff:fe01:d417

[stderr =====>] :
SSH binary not found, using native Go implementation
&{{{<nil> 0 [] [] []} docker [0x853140] <nil>  [] 0s} fd65:76f8:30e8:1:215:5dff:fe01:d417 22 <nil> <nil>}
About to run SSH command:
sudo hostname minikube && echo "minikube" | sudo tee /etc/hostname
Error dialing TCP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported
methods remain
Error dialing TCP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported
methods remain
Error dialing TCP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported
methods remain
Error dialing TCP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported
methods remain

tjsb · 2017-09-20T15:05:22Z

I am having the same issue.

maarten-daalder-isaac · 2017-09-21T08:01:06Z

On Windows 10 the build provided by IljaKroonen works now, before I had the weird /var/...\var...\certs issue as well.

I started Minikube with the following command:
minikube start --vm-driver hyperv --hyperv-virtual-switch minikube-virt-switch --kubernetes-version v1.7.5 -v 999 --disk-size 4g
Then I could run minikube dashboard without problems.

secat · 2017-09-21T18:28:11Z

@r2d4 Is there going to be an official release version 0.22.3?

EricssonVNFCloud · 2017-09-21T21:53:33Z

On Windows 10 the build provided by IljaKroonen works now, before I had the weird /var/...\var...\certs issue as well.

I started Minikube with the following command:
minikube start --vm-driver hyperv --hyperv-virtual-switch minikube-virt-switch --kubernetes-version v1.7.5 -v 999 --disk-size 4g
Then I could run minikube dashboard without problems.

Can you provide more details ??
What is your hyperv version ??
Windows 10 , 32 bit or 64 bit ??

EricssonVNFCloud · 2017-09-21T21:53:50Z

Seems minikube is Jinxed on Windows.

richardjharding · 2017-09-22T07:31:04Z

I had the same experience -at first the build linked above failed with cert issues but after deleting and issuing another minikube start its all working

win10 build 15063.608
minikube is reporting 0.22.2 but its the build from link to 1982 above
hyperv 10.0.15063.502

hope that helps

maarten-daalder-isaac · 2017-09-22T08:02:09Z

Hi @EricssonVNFCloud,

64bit Windows 10, version 1703 OS build 15063.608
HyperV version 10.0.15063.502

Of course, I had to create a virtual switch first.

rwenz3l · 2017-09-25T13:23:39Z

Same for me with virtualbox. Seems to be resolved, when creating a new machine with the build 1982 that was linked.

endophage · 2017-10-01T20:15:56Z

Build 1982 is failing on startup for me.

OS: Windows 10 Pro
minikube: @IljaKroonen's build linked above
Hyper-V: 10.0.15063.0

$PS>  minikube start -v 10 --vm-driver=hyperv --hyperv-virtual-switch=<my external switch>
...
setting hostname "minikube"
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM minikube ).networkadapters[0]).ipaddresses[0]
[stdout =====>] : 192.168.0.107

[stderr =====>] :
Using SSH client type: native
&{{{<nil> 0 [] [] []} docker [0x853140] <nil>  [] 0s} 192.168.0.107 22 <nil> <nil>}
About to run SSH command:
sudo hostname minikube && echo "minikube" | sudo tee /etc/hostname
Error dialing TCP: dial tcp 192.168.0.107:22: connectex: No connection could be made because the target machine actively refused it.```

Then it just retries every few seconds, printing that final line of the log over and over.

JacekFeliksiakMYOB · 2017-10-04T00:02:25Z

Hi there,

edit
I edited this message, because it is highly possible that it is cause by docker-machine:(
edit

I have the same problem after IljaKroonen build 1982. Before and after this changes I have the same status:

C:\Kubernetes\Workspace>minikube status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at fe80::215:5dff:fe32:871a

my comand:

minikube start --kubernetes-version="v1.7.5" --vm-driver="hyperv" --memory=1024 --hyperv-virtual-switch="switch" --v=7 --alsologtostderr

my virtual switch - external / Ethernet

I am adding some logs

Oct 04 00:04:07 minikube systemd[1]: Starting Localkube...
Oct 04 00:04:08 minikube localkube[2730]: proto: duplicate proto type registered: google.protobuf.Any
Oct 04 00:04:08 minikube localkube[2730]: proto: duplicate proto type registered: google.protobuf.Duration
Oct 04 00:04:08 minikube localkube[2730]: proto: duplicate proto type registered: google.protobuf.Timestamp
Oct 04 00:04:08 minikube localkube[2730]: listening for peers on http://localhost:2380
Oct 04 00:04:08 minikube localkube[2730]: listening for client requests on localhost:2379
Oct 04 00:04:08 minikube localkube[2730]: name = default
Oct 04 00:04:08 minikube localkube[2730]: data dir = /var/lib/localkube/etcd
Oct 04 00:04:08 minikube localkube[2730]: member dir = /var/lib/localkube/etcd/member
Oct 04 00:04:08 minikube localkube[2730]: heartbeat = 100ms
Oct 04 00:04:08 minikube localkube[2730]: election = 1000ms
Oct 04 00:04:08 minikube localkube[2730]: snapshot count = 10000
Oct 04 00:04:08 minikube localkube[2730]: advertise client URLs = http://localhost:2379
Oct 04 00:04:08 minikube localkube[2730]: initial advertise peer URLs = http://localhost:2380
Oct 04 00:04:08 minikube localkube[2730]: initial cluster = default=http://localhost:2380
Oct 04 00:04:08 minikube localkube[2730]: starting member 8e9e05c52164694d in cluster cdf818194e3a8c32
Oct 04 00:04:08 minikube localkube[2730]: 8e9e05c52164694d became follower at term 0
Oct 04 00:04:08 minikube localkube[2730]: newRaft 8e9e05c52164694d [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
Oct 04 00:04:08 minikube localkube[2730]: 8e9e05c52164694d became follower at term 1
Oct 04 00:04:08 minikube localkube[2730]: starting server... [version: 3.1.5, cluster version: to_be_decided]
Oct 04 00:04:08 minikube localkube[2730]: added member 8e9e05c52164694d [http://localhost:2380] to cluster cdf818194e3a8c32
Oct 04 00:04:09 minikube localkube[2730]: 8e9e05c52164694d is starting a new election at term 1
Oct 04 00:04:09 minikube localkube[2730]: 8e9e05c52164694d became candidate at term 2
Oct 04 00:04:09 minikube localkube[2730]: 8e9e05c52164694d received MsgVoteResp from 8e9e05c52164694d at term 2
Oct 04 00:04:09 minikube localkube[2730]: 8e9e05c52164694d became leader at term 2
Oct 04 00:04:09 minikube localkube[2730]: raft.node: 8e9e05c52164694d elected leader 8e9e05c52164694d at term 2
Oct 04 00:04:09 minikube localkube[2730]: setting up the initial cluster version to 3.1
Oct 04 00:04:09 minikube localkube[2730]: set the initial cluster version to 3.1
Oct 04 00:04:09 minikube localkube[2730]: enabled capabilities for version 3.1
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.330651    2730 etcd.go:58] Etcd server is ready
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.330735    2730 interface.go:259] No valid IP found
Oct 04 00:04:09 minikube localkube[2730]: localkube host ip address: <nil>
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.330756    2730 plugins.go:77] Registered admission plugin "NamespaceLifecycle"
Oct 04 00:04:09 minikube localkube[2730]: Starting apiserver...
Oct 04 00:04:09 minikube localkube[2730]: Waiting for apiserver to be healthy...
Oct 04 00:04:09 minikube localkube[2730]: published {Name:default ClientURLs:[http://localhost:2379]} to cluster cdf818194e3a8c32
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333631    2730 server.go:112] Version: v1.7.5
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333712    2730 plugins.go:77] Registered admission plugin "AlwaysAdmit"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333717    2730 plugins.go:77] Registered admission plugin "AlwaysPullImages"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333720    2730 plugins.go:77] Registered admission plugin "LimitPodHardAntiAffinityTopology"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333724    2730 plugins.go:77] Registered admission plugin "DefaultTolerationSeconds"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333727    2730 plugins.go:77] Registered admission plugin "AlwaysDeny"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333730    2730 plugins.go:77] Registered admission plugin "DenyEscalatingExec"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333733    2730 plugins.go:77] Registered admission plugin "DenyExecOnPrivileged"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333737    2730 plugins.go:77] Registered admission plugin "OwnerReferencesPermissionEnforcement"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333745    2730 plugins.go:77] Registered admission plugin "ImagePolicyWebhook"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333750    2730 plugins.go:77] Registered admission plugin "Initializers"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333755    2730 plugins.go:77] Registered admission plugin "InitialResources"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333760    2730 plugins.go:77] Registered admission plugin "LimitRanger"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333765    2730 plugins.go:77] Registered admission plugin "NamespaceAutoProvision"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333832    2730 plugins.go:77] Registered admission plugin "NamespaceExists"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333890    2730 plugins.go:77] Registered admission plugin "NodeRestriction"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333903    2730 plugins.go:77] Registered admission plugin "PersistentVolumeLabel"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.333962    2730 plugins.go:77] Registered admission plugin "PodNodeSelector"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.334019    2730 plugins.go:77] Registered admission plugin "PodPreset"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.334027    2730 plugins.go:77] Registered admission plugin "PodTolerationRestriction"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.334116    2730 plugins.go:77] Registered admission plugin "ResourceQuota"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.334180    2730 plugins.go:77] Registered admission plugin "PodSecurityPolicy"
Oct 04 00:04:09 minikube localkube[2730]: ready to serve client requests
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.334239    2730 plugins.go:77] Registered admission plugin "SecurityContextDeny"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.334246    2730 plugins.go:77] Registered admission plugin "ServiceAccount"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.334293    2730 plugins.go:77] Registered admission plugin "DefaultStorageClass"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.334428    2730 plugins.go:77] Registered admission plugin "GenericAdmissionWebhook"
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.335028    2730 interface.go:259] No valid IP found
Oct 04 00:04:09 minikube localkube[2730]: apiserver: Exit with error: Unable to find suitable network address.error='Unable to select an IP.'. Try to set the AdvertiseAddress directly or provide a valid BindAddress to fix this.
Oct 04 00:04:09 minikube localkube[2730]: serving insecure client requests on 127.0.0.1:2379, this is strongly discouraged!
Oct 04 00:04:09 minikube localkube[2730]: I1004 00:04:09.535416    2730 server.go:112] Version: v1.7.5
Oct 04 00:04:09 minikube localkube[2730]: F1004 00:04:09.535454    2730 plugins.go:72] Admission plugin "AlwaysAdmit" was registered twice
Oct 04 00:04:09 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=255/n/a
Oct 04 00:04:09 minikube systemd[1]: Failed to start Localkube.
Oct 04 00:04:09 minikube systemd[1]: localkube.service: Unit entered failed state.
Oct 04 00:04:09 minikube systemd[1]: localkube.service: Failed with result 'exit-code'.
Oct 04 00:04:12 minikube systemd[1]: localkube.service: Service hold-off time over, scheduling restart.
Oct 04 00:04:12 minikube systemd[1]: Stopped Localkube.
Oct 04 00:04:12 minikube systemd[1]: Starting Localkube...
Oct 04 00:04:12 minikube localkube[2781]: proto: duplicate proto type registered: google.protobuf.Any
Oct 04 00:04:12 minikube localkube[2781]: proto: duplicate proto type registered: google.protobuf.Duration
Oct 04 00:04:12 minikube localkube[2781]: proto: duplicate proto type registered: google.protobuf.Timestamp
Oct 04 00:04:12 minikube localkube[2781]: listening for peers on http://localhost:2380
Oct 04 00:04:12 minikube localkube[2781]: listening for client requests on localhost:2379
Oct 04 00:04:12 minikube localkube[2781]: name = default
Oct 04 00:04:12 minikube localkube[2781]: data dir = /var/lib/localkube/etcd
Oct 04 00:04:12 minikube localkube[2781]: member dir = /var/lib/localkube/etcd/member
Oct 04 00:04:12 minikube localkube[2781]: heartbeat = 100ms
Oct 04 00:04:12 minikube localkube[2781]: election = 1000ms
Oct 04 00:04:12 minikube localkube[2781]: snapshot count = 10000
Oct 04 00:04:12 minikube localkube[2781]: advertise client URLs = http://localhost:2379
Oct 04 00:04:12 minikube localkube[2781]: restarting member 8e9e05c52164694d in cluster cdf818194e3a8c32 at commit index 4
Oct 04 00:04:12 minikube localkube[2781]: 8e9e05c52164694d became follower at term 2
Oct 04 00:04:12 minikube localkube[2781]: newRaft 8e9e05c52164694d [peers: [], term: 2, commit: 4, applied: 0, lastindex: 4, lastterm: 2]
Oct 04 00:04:12 minikube localkube[2781]: starting server... [version: 3.1.5, cluster version: to_be_decided]
Oct 04 00:04:12 minikube localkube[2781]: added member 8e9e05c52164694d [http://localhost:2380] to cluster cdf818194e3a8c32
Oct 04 00:04:12 minikube localkube[2781]: set the initial cluster version to 3.1
Oct 04 00:04:12 minikube localkube[2781]: enabled capabilities for version 3.1
Oct 04 00:04:13 minikube localkube[2781]: 8e9e05c52164694d is starting a new election at term 2
Oct 04 00:04:13 minikube localkube[2781]: 8e9e05c52164694d became candidate at term 3
Oct 04 00:04:13 minikube localkube[2781]: 8e9e05c52164694d received MsgVoteResp from 8e9e05c52164694d at term 3
Oct 04 00:04:13 minikube localkube[2781]: 8e9e05c52164694d became leader at term 3
Oct 04 00:04:13 minikube localkube[2781]: raft.node: 8e9e05c52164694d elected leader 8e9e05c52164694d at term 3
Oct 04 00:04:13 minikube localkube[2781]: published {Name:default ClientURLs:[http://localhost:2379]} to cluster cdf818194e3a8c32
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.260097    2781 etcd.go:58] Etcd server is ready
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.260252    2781 interface.go:259] No valid IP found
Oct 04 00:04:13 minikube localkube[2781]: localkube host ip address: <nil>
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.260425    2781 plugins.go:77] Registered admission plugin "NamespaceLifecycle"
Oct 04 00:04:13 minikube localkube[2781]: Starting apiserver...
Oct 04 00:04:13 minikube localkube[2781]: Waiting for apiserver to be healthy...
Oct 04 00:04:13 minikube localkube[2781]: ready to serve client requests
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.260847    2781 server.go:112] Version: v1.7.5
Oct 04 00:04:13 minikube localkube[2781]: serving insecure client requests on 127.0.0.1:2379, this is strongly discouraged!
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261013    2781 plugins.go:77] Registered admission plugin "AlwaysAdmit"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261098    2781 plugins.go:77] Registered admission plugin "AlwaysPullImages"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261178    2781 plugins.go:77] Registered admission plugin "LimitPodHardAntiAffinityTopology"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261259    2781 plugins.go:77] Registered admission plugin "DefaultTolerationSeconds"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261340    2781 plugins.go:77] Registered admission plugin "AlwaysDeny"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261423    2781 plugins.go:77] Registered admission plugin "DenyEscalatingExec"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261503    2781 plugins.go:77] Registered admission plugin "DenyExecOnPrivileged"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261584    2781 plugins.go:77] Registered admission plugin "OwnerReferencesPermissionEnforcement"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261677    2781 plugins.go:77] Registered admission plugin "ImagePolicyWebhook"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261757    2781 plugins.go:77] Registered admission plugin "Initializers"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261837    2781 plugins.go:77] Registered admission plugin "InitialResources"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261916    2781 plugins.go:77] Registered admission plugin "LimitRanger"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.261995    2781 plugins.go:77] Registered admission plugin "NamespaceAutoProvision"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.262076    2781 plugins.go:77] Registered admission plugin "NamespaceExists"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.262203    2781 plugins.go:77] Registered admission plugin "NodeRestriction"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.262290    2781 plugins.go:77] Registered admission plugin "PersistentVolumeLabel"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.262371    2781 plugins.go:77] Registered admission plugin "PodNodeSelector"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.262454    2781 plugins.go:77] Registered admission plugin "PodPreset"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.262541    2781 plugins.go:77] Registered admission plugin "PodTolerationRestriction"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.263735    2781 plugins.go:77] Registered admission plugin "ResourceQuota"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.263969    2781 plugins.go:77] Registered admission plugin "PodSecurityPolicy"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.264086    2781 plugins.go:77] Registered admission plugin "SecurityContextDeny"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.264207    2781 plugins.go:77] Registered admission plugin "ServiceAccount"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.264355    2781 plugins.go:77] Registered admission plugin "DefaultStorageClass"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.264537    2781 plugins.go:77] Registered admission plugin "GenericAdmissionWebhook"
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.264770    2781 interface.go:259] No valid IP found
Oct 04 00:04:13 minikube localkube[2781]: apiserver: Exit with error: Unable to find suitable network address.error='Unable to select an IP.'. Try to set the AdvertiseAddress directly or provide a valid BindAddress to fix this.
Oct 04 00:04:13 minikube localkube[2781]: I1004 00:04:13.465233    2781 server.go:112] Version: v1.7.5
Oct 04 00:04:13 minikube localkube[2781]: F1004 00:04:13.465292    2781 plugins.go:72] Admission plugin "AlwaysAdmit" was registered twice
Oct 04 00:04:13 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=255/n/a
Oct 04 00:04:13 minikube systemd[1]: Failed to start Localkube.
Oct 04 00:04:13 minikube systemd[1]: localkube.service: Unit entered failed state.
Oct 04 00:04:13 minikube systemd[1]: localkube.service: Failed with result 'exit-code'.

BlitzkriegSoftware · 2017-10-09T21:55:51Z

My cluster has a status of stopped as well. Windows 10 + Hyper-V (and yes there is a virtual-switch)

minikube start --kubernetes-version "v1.7.5" --vm-driver "hyperv" --memory=1024 --hyperv-virtual-switch "MiniKubeSwitch" -v 999 --disk-size 4g --alsologtostderr

Result:

>minikube.exe status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at 10.0.0.44

What else can I provide to help fix this issue?

r2d4 · 2017-10-10T00:52:09Z

This should be fixed by the latest release 0.22.3

VenkateshSrini · 2017-10-10T03:53:24Z

Hi,
Now I see that the cluster is also running. I typed the command kubectl cluster-info. The output is as below
Kubernetes master is running at https://192.168.0.111:8443
error: group map[authentication.k8s.io:0xc082307dc0 extensions:0xc0823be310 rbac.authorization.k8s.io:0xc0823be3f0 stora
ge.k8s.io:0xc0823be460 batch:0xc0823be150 certificates.k8s.io:0xc0823be1c0 componentconfig:0xc0823be230 federation:0xc08
2307810 :0xc082307ce0 apps:0xc082307d50 authorization.k8s.io:0xc082307f10 autoscaling:0xc082307f80 policy:0xc0823be380]
is already registered
I tried accessing the URL https://192.168.0.111:8443/api/v1/proxy/names%20paces/kube-system/services/kubernetes-dashboard
I get Unauthorized error.
I tried accessing the url https://192.168.0.111:8443
then also getting unauthorized error.
Please help as I think I'm in the last step of setting up the minikube on my windows 10 machine

richardjharding · 2017-10-10T08:10:24Z

Hi
I sometimes see something similar - usually when the ip of the vm has changed eg when you change network connections on the host machine

Do you see anything when you do

minikube dashboard

it should pop up a browser with the dashboard - if not then what usually resolves it for me is

minikube stop
minikube start

That seems to sort out the certificates then minikube dashboard should work

VenkateshSrini · 2017-10-10T11:23:22Z

Hi,
My Bad. I updated the kubectl to 1.8.0. It is working now

rlitman-10c · 2017-10-10T11:59:27Z

Just tested on 0.22.3, it still happens (I did a clean install - removed the VM, .minikube, etc...). In previous versions (0.22.*) I once saw a kernel panic in minikube VM (but I don't know where to find logs for that event), machine restarted and docker daemon was running, but there were no k8s containers. As we use dhcp, the VM's IP address gets changed every time this happens, so my guess is VM gets restarted and that causes the k8s inside to "die".

> minikube version
minikube version: v0.22.3
>  minikube status
minikube: Running
cluster: Stopped
kubectl: Misconfigured: pointing to stale minikube-vm.
To fix the kubectl context, run minikube update-context
> minikube update-context
Reconfigured kubeconfig IP, now pointing at 10.10.102.115
> minikube status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at 10.10.102.115

BlitzkriegSoftware · 2017-10-10T17:27:31Z

Ditto! 0.22.3 cluster is still stopped. Is there a log I can send you?

AneetaGeorge · 2017-10-13T05:03:45Z

Hi, I'm facing similar issues. "minikube start" starts the cluster but when i try to run anything with kubectl it says "unable to connect to server : Service unavailable". Can someone please help me?

maarten-daalder-isaac · 2017-10-13T05:50:09Z

Using Hyper-V on Windows 10 Creator Update I had to do the following:

Use a virtual switch that is bridged to a real network (External), because Hyper-V does not supply DHCP/DNS/Gateway server(s).
Set a fixed MAC address, otherwise it would suddenly get a new IP address which messes things up
Set a fixed memory amount, by default it gradually reduces the memory

AneetaGeorge · 2017-10-13T10:02:50Z

I'm using virtualbox in windows 10 64 bit . Is there any more details that I should provide?I'm really new to kubernetes

shahrouzz · 2017-10-31T22:11:32Z

I have similar issues with minikube 0.23 on windows 10 with the hyperv driver.
Everything starts up fine and then there is a kernel panic after using the cluster for a minute or two.

minikube 0.19.1 runs fine on with the same setup.

neoGeneva · 2017-11-02T20:39:24Z

I'm also seeing a kernel panic with minikube v0.23.0 on Windows 10 using the hyperv driver.

I get it pretty reliably while trying to install fabric8 using gofabric8 deploy --package system -n fabric8

I'm not familiar with debugging kernel panics, so I couldn't figure out how to use get any more of the log out other than what was displayed in the console:

[  1817.969079]  0000000000000000 ffffc90002acbe40 ffffffffa0002ae5 ffffffff813ee645
[  1817.969079] Call Trace: 
[  1817.969079]  [<ffffffff810bd9e3>] ? del_timer_sync+0x43/0x50
[  1817.969079]  [<ffffffffa0002ae5>] vmbus_sendpacket_ctl+0xa5/0xb0 [hv_vmbus]
[  1817.969079]  [<ffffffff813ee645>] ? find_next_bit+0x15/0x20
[  1817.969079]  [<ffffffffa0002b04>] vmbus_sendpacket+0x14/0x20 [hv_vmbus]
[  1817.969079]  [<ffffffffa0081374>] post_status+0x104/0x110 [hv_balloon]
[  1817.969079]  [<ffffffffa0081380>] ? post_status+0x110/0x110 [hv_balloon]
[  1817.969079]  [<ffffffffa00813ad>] dm_thread_func+0x2d/0x40 [hv_balloon]
[  1817.969079]  [<ffffffff8107b145>] kthread+0xc5/0xe0
[  1817.969079]  [<ffffffff8107b080>] ? kthread_park+0x60/0x60
[  1817.969079]  [<ffffffff819e1005>] ret_from_fork+0x25/0x30
[  1817.969079] Code: 13 08 44 39 e0 75 ed 44 8d 69 08 80 7d d0 00 48 c7 45 b8 00 00 00 00 0f 85 2e 01 00 00 49 8b 97 f8 00 00 00 41 8b 87 08 01 00 00 <8b> 72 04 8b 3a 89 f1 89 7d c4 29 f9 39 fe 77 06 89 c1 29 f9 01
[  1817.969079] RIP  [<ffffffffa0004d30>] hv_ringbuffer_write+0x60/0x1d0 [hv_vmbus]
[  1817.969079]  RSP <ffffc90002acbd98>
[  1817.969079] CR2: ffffc90002aa9004
[  1817.969079] ---[ end trace lcff63732a36dce0 ]---
[  1817.969079] Kernel panic - not syncing: Fatal exception
[  1817.969079] Kernel Offset: disabled
[  1817.969079] Rebooting in 10 seconds..

SGA-liu-yin · 2017-11-07T05:09:31Z

Hey guys

I could reproduce this issue in the latest minikube on Windows 8.1

Environment:

Minikube version: minikube version: v0.23.0

OS: Windows 8.1 64-bit
VM Driver: VirtualBox
Install tools: n/a
Others: n/a

What happened:

After restarted windows without stopping minikube vm,
Next time, the minikube provisioned the VM, but it does not work correctly.

What you expected to happen:
The Minikube cluster should work correctly.

How to reproduce it (as minimally and precisely as possible):

Downloaded minikube 0.23.0 and placed it in my PATH.
Deleted C:/users/user/.minikube and C:/users/user/.kube
Ran minikube start.
The VM provisions correctly.
Tried to do something with the minikube (e.x deploying wordpress, mysql)
Then, shutdown/restart your PC without stopping the minikube vm
Finally, after we re-start the minikube, it could not work correct anymore.

$ minikube dashboard
Could not find finalized endpoint being pointed to by kubernetes-dashboard: Error validating service: Error getting service kubernetes-dashboard: Get https://192.168.99.100:8443/api/v1/namespaces/kube-system/services/kubernetes-dashboard: dial tcp 192.168.99.100:8443: connectex: No connection could be made because the target machine actively refused it.

$ minikube status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100

after checking the logs

I noticed one issue:

Nov 07 05:20:29 minikube localkube[20600]: cannot commit tx (write /var/lib/localkube/etcd/member/snap/db: file too large)
Nov 07 05:20:29 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=1/FAILURE

More logs listed as below

$ minikube logs
-- Logs begin at Tue 2017-11-07 04:57:55 UTC, end at Tue 2017-11-07 04:58:18 UTC. --
Nov 07 04:58:10 minikube systemd[1]: Starting Localkube...
Nov 07 04:58:11 minikube localkube[3110]: listening for peers on http://localhost:2380
Nov 07 04:58:11 minikube localkube[3110]: listening for client requests on localhost:2379
Nov 07 04:58:11 minikube localkube[3110]: recovered store from snapshot at index 50005
Nov 07 04:58:11 minikube localkube[3110]: name = default
Nov 07 04:58:11 minikube localkube[3110]: data dir = /var/lib/localkube/etcd
Nov 07 04:58:11 minikube localkube[3110]: member dir = /var/lib/localkube/etcd/member
Nov 07 04:58:11 minikube localkube[3110]: heartbeat = 100ms
Nov 07 04:58:11 minikube localkube[3110]: election = 1000ms
Nov 07 04:58:11 minikube localkube[3110]: snapshot count = 10000
Nov 07 04:58:11 minikube localkube[3110]: advertise client URLs = http://localhost:2379
Nov 07 04:58:11 minikube localkube[3110]: restarting member 8e9e05c52164694d in cluster cdf818194e3a8c32 at commit index 50673
Nov 07 04:58:11 minikube localkube[3110]: 8e9e05c52164694d became follower at term 6
Nov 07 04:58:11 minikube localkube[3110]: newRaft 8e9e05c52164694d [peers: [8e9e05c52164694d], term: 6, commit: 50673, applied: 50005, lastindex: 50673, lastterm: 6]
Nov 07 04:58:11 minikube localkube[3110]: enabled capabilities for version 3.1
Nov 07 04:58:11 minikube localkube[3110]: added member 8e9e05c52164694d [http://localhost:2380] to cluster cdf818194e3a8c32 from store
Nov 07 04:58:11 minikube localkube[3110]: set the cluster version to 3.1 from store
Nov 07 04:58:11 minikube localkube[3110]: cannot commit tx (write /var/lib/localkube/etcd/member/snap/db: file too large)
Nov 07 04:58:11 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=1/FAILURE
Nov 07 04:58:11 minikube systemd[1]: Failed to start Localkube.
Nov 07 04:58:11 minikube systemd[1]: localkube.service: Unit entered failed state.
Nov 07 04:58:11 minikube systemd[1]: localkube.service: Failed with result 'exit-code'.
Nov 07 04:58:14 minikube systemd[1]: localkube.service: Service hold-off time over, scheduling restart.
Nov 07 04:58:14 minikube systemd[1]: Stopped Localkube.
Nov 07 04:58:14 minikube systemd[1]: Starting Localkube...
Nov 07 04:58:14 minikube localkube[3170]: listening for peers on http://localhost:2380
Nov 07 04:58:14 minikube localkube[3170]: listening for client requests on localhost:2379
Nov 07 04:58:14 minikube localkube[3170]: recovered store from snapshot at index 50005
Nov 07 04:58:14 minikube localkube[3170]: name = default
Nov 07 04:58:14 minikube localkube[3170]: data dir = /var/lib/localkube/etcd
Nov 07 04:58:14 minikube localkube[3170]: member dir = /var/lib/localkube/etcd/member
Nov 07 04:58:14 minikube localkube[3170]: heartbeat = 100ms
Nov 07 04:58:14 minikube localkube[3170]: election = 1000ms
Nov 07 04:58:14 minikube localkube[3170]: snapshot count = 10000
Nov 07 04:58:14 minikube localkube[3170]: advertise client URLs = http://localhost:2379
Nov 07 04:58:14 minikube localkube[3170]: restarting member 8e9e05c52164694d in cluster cdf818194e3a8c32 at commit index 50673
Nov 07 04:58:14 minikube localkube[3170]: 8e9e05c52164694d became follower at term 6
Nov 07 04:58:14 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=1/FAILURE
Nov 07 04:58:14 minikube systemd[1]: Failed to start Localkube.
Nov 07 04:58:14 minikube systemd[1]: localkube.service: Unit entered failed state.
Nov 07 04:58:14 minikube systemd[1]: localkube.service: Failed with result 'exit-code'.
Nov 07 04:58:18 minikube systemd[1]: localkube.service: Service hold-off time over, scheduling restart.
Nov 07 04:58:18 minikube systemd[1]: Stopped Localkube.
Nov 07 04:58:18 minikube systemd[1]: Starting Localkube...
Nov 07 04:58:18 minikube localkube[3205]: listening for peers on http://localhost:2380
Nov 07 04:58:18 minikube localkube[3205]: listening for client requests on localhost:2379
Nov 07 04:58:18 minikube localkube[3205]: recovered store from snapshot at index 50005
Nov 07 04:58:18 minikube localkube[3205]: name = default
Nov 07 04:58:18 minikube localkube[3205]: data dir = /var/lib/localkube/etcd
Nov 07 04:58:18 minikube localkube[3205]: member dir = /var/lib/localkube/etcd/member
Nov 07 04:58:18 minikube localkube[3205]: heartbeat = 100ms
Nov 07 04:58:18 minikube localkube[3205]: election = 1000ms
Nov 07 04:58:18 minikube localkube[3205]: snapshot count = 10000
Nov 07 04:58:18 minikube localkube[3205]: advertise client URLs = http://localhost:2379
Nov 07 04:58:18 minikube localkube[3205]: restarting member 8e9e05c52164694d in cluster cdf818194e3a8c32 at commit index 50673
Nov 07 04:58:18 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=1/FAILURE
Nov 07 04:58:18 minikube systemd[1]: Failed to start Localkube.
Nov 07 04:58:18 minikube systemd[1]: localkube.service: Unit entered failed state.
Nov 07 04:58:18 minikube systemd[1]: localkube.service: Failed with result 'exit-code'.

gbraad · 2017-11-07T05:35:40Z

@neoGeneva was the kernel panic reproducible? it looks like an issue with the hypervisor communication driver. This is not really actively used in the Minikube iso, except for sending the IP address to the hypervisor over hvkvp AFAIR.

neoGeneva · 2017-11-07T08:23:51Z

@gbraad yeah, every time I try and install fabric8 (version 0.4.173) it has a kernel panic after a five or six minutes, even with a fresh install of minikube.

minikube logs returns -- No entries -- after the VM reboots, and I tried getting more logs out with netconsole, but I'm not familiar enough with debugging on Linux to get it going.

If there is anything else I can provide please let me know.

neoGeneva · 2017-11-12T09:36:28Z

@gbraad Just letting you know that I'm still seeing the issue even without fabric8, seems to be after about every 15-20 minutes I get a kernel panic.

gbraad · 2017-11-13T04:19:33Z

@neoGeneva this is a different issue, but can you share your system configuration, host OS, etc. Have you also tried using any other ISO (previous version or B2D)?

neoGeneva · 2017-11-14T21:45:51Z

@gbraad I think this is probably a different issue from this one, so I've opened a new issue: #2195

barbarosalp · 2017-12-28T06:53:56Z

PS X:\Playground\kubernetesplay> minikube status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.2.50

When the cluster is in this state above, just executing minikube start fixed the issue for me.

raghur · 2018-01-10T04:24:13Z

I'm having this issue as well - win 8.1 x64/Vbox

>minikube version
minikube version: v0.24.1

>minikube status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100

Tried running minikube start again as noted by @barbarosalp but no change.

minikube logs (snipped)

Jan 10 04:20:56 minikube localkube[5430]: goroutine 126 [running]:
Jan 10 04:20:56 minikube localkube[5430]: k8s.io/minikube/vendor/github.com/boltdb/bolt.(*freelist).free(0xc4208cc540, 0x4da8c, 0x7f29c807f000)
Jan 10 04:20:56 minikube localkube[5430]:         /go/src/k8s.io/minikube/vendor/github.com/boltdb/bolt/freelist.go:117 +0x301
Jan 10 04:20:56 minikube localkube[5430]: k8s.io/minikube/vendor/github.com/boltdb/bolt.(*node).spill(0xc42229c070, 0xc420036b20, 0x7)
Jan 10 04:20:56 minikube localkube[5430]:         /go/src/k8s.io/minikube/vendor/github.com/boltdb/bolt/node.go:363 +0x210
Jan 10 04:20:56 minikube localkube[5430]: k8s.io/minikube/vendor/github.com/boltdb/bolt.(*Bucket).spill(0xc4217dc1d8, 0x15412ccf, 0x9a4b0a0)
Jan 10 04:20:56 minikube localkube[5430]:         /go/src/k8s.io/minikube/vendor/github.com/boltdb/bolt/bucket.go:541 +0x4d3
Jan 10 04:20:56 minikube localkube[5430]: k8s.io/minikube/vendor/github.com/boltdb/bolt.(*Tx).Commit(0xc4217dc1c0, 0x1541201c, 0x9a4b0a0)
Jan 10 04:20:56 minikube localkube[5430]:         /go/src/k8s.io/minikube/vendor/github.com/boltdb/bolt/tx.go:163 +0x129
Jan 10 04:20:56 minikube localkube[5430]: k8s.io/minikube/vendor/github.com/coreos/etcd/mvcc/backend.(*batchTx).commit(0xc4204f6520, 0x4702e00)
Jan 10 04:20:56 minikube localkube[5430]:         /go/src/k8s.io/minikube/vendor/github.com/coreos/etcd/mvcc/backend/batch_tx.go:183 +0x9d
Jan 10 04:20:56 minikube localkube[5430]: k8s.io/minikube/vendor/github.com/coreos/etcd/mvcc/backend.(*batchTx).Commit(0xc4204f6520)
Jan 10 04:20:56 minikube localkube[5430]:         /go/src/k8s.io/minikube/vendor/github.com/coreos/etcd/mvcc/backend/batch_tx.go:140 +0x66
Jan 10 04:20:56 minikube localkube[5430]: k8s.io/minikube/vendor/github.com/coreos/etcd/mvcc/backend.(*backend).run(0xc420224960)
Jan 10 04:20:56 minikube localkube[5430]:         /go/src/k8s.io/minikube/vendor/github.com/coreos/etcd/mvcc/backend/backend.go:199 +0xbb
Jan 10 04:20:56 minikube localkube[5430]: created by k8s.io/minikube/vendor/github.com/coreos/etcd/mvcc/backend.newBackend
Jan 10 04:20:56 minikube localkube[5430]:         /go/src/k8s.io/minikube/vendor/github.com/coreos/etcd/mvcc/backend/backend.go:119 +0x267
Jan 10 04:20:56 minikube systemd[1]: localkube.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 10 04:20:56 minikube systemd[1]: Failed to start Localkube.
Jan 10 04:20:56 minikube systemd[1]: localkube.service: Unit entered failed state.
Jan 10 04:20:56 minikube systemd[1]: localkube.service: Failed with result 'exit-code'.

ALYSShow · 2018-01-26T10:49:15Z

Same issue here. Running minikube start a couple of times doesn't seem to fix it. A restart didn't help as well.

It is worth noting that my setup was working normally for some time then suddenly stopped (might be after a restart without properly stopping minikube and docker-machine).

Windows 10 Home
minikube version: v0.24.1
docker-machine version 0.10.0, build 76ed2a6
Docker version 17.04.0-ce, build 4845c56

ye · 2018-02-13T17:06:45Z

I got the same issue every time my Mac wakes up from sleep(it started okay before going to sleep though).

$ kubectl get pods
The connection to the server 192.168.99.100:8443 was refused - did you specify the right host or port?

$ kubectl cluster-info
Kubernetes master is running at https://192.168.99.100:8443

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

$ kubectl cluster-info dump
The connection to the server 192.168.99.100:8443 was refused - did you specify the right host or port?

$ minikube logs
-- Logs begin at Tue 2018-02-13 15:34:33 UTC, end at Tue 2018-02-13 16:42:02 UTC. --
-- No entries --

$ minikube version
minikube version: v0.25.0

$ minikube status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100

$ docker version
Client:
 Version:       18.02.0-ce
 API version:   1.36
 Go version:    go1.9.3
 Git commit:    fc4de44
 Built: Wed Feb  7 21:13:05 2018
 OS/Arch:       darwin/amd64
 Experimental:  false
 Orchestrator:  swarm

Server:
 Engine:
  Version:      18.02.0-ce
  API version:  1.36 (minimum version 1.12)
  Go version:   go1.9.3
  Git commit:   fc4de44
  Built:        Wed Feb  7 21:20:15 2018
  OS/Arch:      linux/amd64
  Experimental: true

jostyee · 2018-04-26T09:42:35Z

failed on Mac, too.

$ minikube version
minikube version: v0.26.1

$ docker version
Client:
 Version:	18.03.0-ce
 API version:	1.37
 Go version:	go1.9.4
 Git commit:	0520e24
 Built:	Wed Mar 21 23:06:22 2018
 OS/Arch:	darwin/amd64
 Experimental:	false
 Orchestrator:	swarm

Server:
 Engine:
  Version:	18.03.0-ce
  API version:	1.37 (minimum version 1.12)
  Go version:	go1.9.4
  Git commit:	0520e24
  Built:	Wed Mar 21 23:14:32 2018
  OS/Arch:	linux/amd64
  Experimental:	true

$ export {http,https,ftp}_proxy=http://127.0.0.1:8888
export {HTTP,HTTPS,FTP}_PROXY=${http_proxy}

minikube start --vm-driver=hyperkit \
                --docker-env HTTP_PROXY=$http_proxy \
                --docker-env HTTPS_PROXY=$https_proxy \
                --bootstrapper localkube
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
WARNING: The localkube bootstrapper is now deprecated and support for it
will be removed in a future release. Please consider switching to the kubeadm bootstrapper, which
is intended to replace the localkube bootstrapper. To disable this message, run
[minikube config set ShowBootstrapperDeprecationNotification false]
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.

$ minikube status
minikube: Running
cluster: Stopped
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.64.14

last part of start with -v 8 verbose log:

Setting up certs...
Connecting to cluster...
(minikube) Calling .GetURL
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.
Making call to close driver server
(minikube) Calling .Close
Successfully made call to close driver server
Making call to close connection to plugin binary
(minikube) DBG | Closing plugin on server side
Making call to close driver server
(minikube) Calling .Close
Successfully made call to close driver server
Making call to close connection to plugin binary

fejta-bot · 2018-07-25T09:48:55Z

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.

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

fejta-bot · 2018-08-24T10:35:37Z

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

tstromberg · 2018-10-11T16:43:59Z

Closing open localkube issues, as localkube was long deprecated and removed from the last two minikube releases. I hope you were able to find another solution that worked out for you - if not, please open a new PR.

hirsim mentioned this issue Sep 19, 2017

Fix issue 1981 #1982

Merged

zlemisie mentioned this issue Sep 19, 2017

Kubectl cannot connect to minikube api-server on windows 10 #1943

Closed

r2d4 added the os/windows label Sep 21, 2017

richardjharding mentioned this issue Sep 21, 2017

minikube on win10 with Hyperv not started. #1988

Closed

This was referenced Sep 27, 2017

Issue with connecting to Minikube VM #2012

Closed

Minikube Cluster is not running #2009

Closed

hirsim mentioned this issue Oct 9, 2017

Unable to Run Minikube on Windows 10 with Hyper - v #2042

Closed

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 25, 2018

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 24, 2018

tstromberg added the bootstrapper/localkube label Sep 20, 2018

tstromberg changed the title ~~0.22.2 not starting correctly on Windows~~ localkube: panic: unable to read certificate-authority /var/lib/localkube/\var\lib\localkube\certs\ca.crt Sep 20, 2018

tstromberg added the ev/certificate-errors failed due to certificate issues label Sep 20, 2018

tstromberg closed this as completed Oct 11, 2018

localkube: panic: unable to read certificate-authority /var/lib/localkube/\var\lib\localkube\certs\ca.crt #1981

localkube: panic: unable to read certificate-authority /var/lib/localkube/\var\lib\localkube\certs\ca.crt #1981

Comments

F21 commented Sep 19, 2017 • edited Loading

IljaKroonen commented Sep 19, 2017

EricssonVNFCloud commented Sep 19, 2017 • edited by gbraad Loading

IljaKroonen commented Sep 19, 2017

EricssonVNFCloud commented Sep 19, 2017

IljaKroonen commented Sep 19, 2017

EricssonVNFCloud commented Sep 19, 2017

minikube config set WantKubectlDownloadMsg false

EricssonVNFCloud commented Sep 19, 2017

EricssonVNFCloud commented Sep 19, 2017

richardjharding commented Sep 20, 2017

tjsb commented Sep 20, 2017

maarten-daalder-isaac commented Sep 21, 2017

secat commented Sep 21, 2017

EricssonVNFCloud commented Sep 21, 2017

EricssonVNFCloud commented Sep 21, 2017

richardjharding commented Sep 22, 2017

maarten-daalder-isaac commented Sep 22, 2017

rwenz3l commented Sep 25, 2017

endophage commented Oct 1, 2017 • edited Loading

JacekFeliksiakMYOB commented Oct 4, 2017 • edited Loading

BlitzkriegSoftware commented Oct 9, 2017

r2d4 commented Oct 10, 2017

VenkateshSrini commented Oct 10, 2017

richardjharding commented Oct 10, 2017

VenkateshSrini commented Oct 10, 2017

rlitman-10c commented Oct 10, 2017

BlitzkriegSoftware commented Oct 10, 2017

AneetaGeorge commented Oct 13, 2017

maarten-daalder-isaac commented Oct 13, 2017

AneetaGeorge commented Oct 13, 2017

shahrouzz commented Oct 31, 2017

neoGeneva commented Nov 2, 2017 • edited Loading

SGA-liu-yin commented Nov 7, 2017 • edited Loading

gbraad commented Nov 7, 2017 • edited Loading

neoGeneva commented Nov 7, 2017

neoGeneva commented Nov 12, 2017

gbraad commented Nov 13, 2017

neoGeneva commented Nov 14, 2017

barbarosalp commented Dec 28, 2017

raghur commented Jan 10, 2018 • edited Loading

ALYSShow commented Jan 26, 2018

ye commented Feb 13, 2018

jostyee commented Apr 26, 2018

fejta-bot commented Jul 25, 2018

fejta-bot commented Aug 24, 2018

tstromberg commented Oct 11, 2018

F21 commented Sep 19, 2017 •

edited

Loading

EricssonVNFCloud commented Sep 19, 2017 •

edited by gbraad

Loading

endophage commented Oct 1, 2017 •

edited

Loading

JacekFeliksiakMYOB commented Oct 4, 2017 •

edited

Loading

neoGeneva commented Nov 2, 2017 •

edited

Loading

SGA-liu-yin commented Nov 7, 2017 •

edited

Loading

gbraad commented Nov 7, 2017 •

edited

Loading

raghur commented Jan 10, 2018 •

edited

Loading