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

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:

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 16
Comments: 45 (4 by maintainers)

Most upvoted comments

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

+34

IljaKroonen on Sep 19, 2017

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

ye on Feb 13, 2018

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

rlitman-10c on Oct 10, 2017

@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.

neoGeneva on Nov 12, 2017

@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 on Nov 7, 2017

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

BlitzkriegSoftware on Oct 10, 2017

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.

maarten-daalder-isaac on Sep 21, 2017