minikube: Moving files into cluster fails: open ~/.minikube/cache/localkube/localkube-v1.9.0: no such file or directory

I downloaded it from https://github.com/kubernetes/minikube/releases/download/v0.25.0/localkube then I copied the file in ~/.minikube/cache/localkube/localkube-v1.9.0 It seems to start

.minikube/cache/localkube$ minikube start
Starting local Kubernetes v1.9.0 cluster...
Starting VM...
Getting VM IP address...
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.

Possible workaround:

Download this file: https://github.com/kubernetes/minikube/releases/download/v0.25.0/localkube rename it to localkube-v1.9.0 and place it in: /Users/<myuser>/.minikube/cache/localkube/

@dstroot Try http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy

   minikube delete
   minikube start

Seems to have done it for me.

FWIW, in case this helps someone else, I hadn’t used minikube in quite a while (was previously using it with various drivers). I was running into errors with the previously used drivers (vmwarefusion) that used to work:

Was getting errors like:

E0523 12:17:57.956491 6812 start.go:165] Error starting host: Error creating host: Error executing step: Creating VM. : exit status 1

sw_vers
ProductName:	Mac OS X
ProductVersion:	10.11.6
BuildVersion:	15G20015

Updated minikube using brew cask

minikube version
minikube version: v0.27.0

Switching (and installing) updated hyperkit driver (updated xhyve also worked for me although it now barks about it being deprecated)–Followed the doc/process here–i.e.: ref: https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#hyperkit-driver

curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-hyperkit \
> && chmod +x docker-machine-driver-hyperkit \
> && sudo mv docker-machine-driver-hyperkit /usr/local/bin/ \
> && sudo chown root:wheel /usr/local/bin/docker-machine-driver-hyperkit \
> && sudo chmod u+s /usr/local/bin/docker-machine-driver-hyperkit

As others noted above, purge our old cruft minikube delete Then was able to start minikube again without failures minikube start --cpus 4 --memory 4096 --vm-driver=hyperkit --insecure-registry="0.0.0.0/0" -v 5

I am seeing this error now when trying to access the dashboard:

Error: 'tls: oversized record received with length 20527'
Trying to reach: 'https://172.17.0.2:9090/'

I had the same dashboard issue as @dstroot on kubernetes 1.9.0 on OSX:

Error: 'tls: oversized record received with length 20527'
Trying to reach: 'https://172.17.0.2:9090/'

Using the http://localhost:8001/ui/ link which redirects to http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/ with the error.

Solution: Using http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy as suggested by @steindaniel fixed the problem (but maybe at the expense of disabling https?).

@lazzarello did your dashboard come up with the minikube binary and 1.8.0? Mine did not. I’m also seeing a new error when I try 1.9.0.

Starting local Kubernetes v1.9.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
E0126 15:20:16.503730    7219 start.go:234] Error updating cluster:  Error running scp command: sudo scp -t /usr/local/bin output: scp: Broken pipe

I believe I have run into this issue in the past.

I basically had started minikube with --kubernetes-version="v1.8.0" then stopped it, then started it again, this time without --kubernetes-version="v1.8.0":

minikube start --kubernetes-version="v1.8.0"
minikube stop
minikube start

The 2nd start ends up trying to use kubernetes 1.9.0 instead of 1.8.0.

I fixed this by,

1. Stopping minikube minikube stop
2. Editing ~/.minikube/profiles/minikube/config.json and replacing the string v1.9.0 to v1.8.0 (towards the end of the file in the KubernetesConfig section)
3. Starting minikube again, with --kubernetes-version="v1.8.0": minikube start --kubernetes-version="v1.8.0"

Edit: After re-reading this thread, it seems people specifically want to use 1.9.0, in which case I also ran into this bug (and also another one that is that minikube does not remember me wanting to use 1.8.0), but my comment is not the fix you’re looking for.

I’m still having the issue. I’m able to get the same result as doing the curl request e.g. minikube is accessible through kubectl but dashboard is not functional:

brew cask reinstall minikube

minikube start --vm-driver=hyperkit \
    --kubernetes-version="v1.8.0" \
    --iso-url="https://storage.googleapis.com/minikube/iso/minikube-v0.24.0.iso"

does not seem to help:

kgi-mbp-i7-2:~ kgignatyev$ mv ~/Downloads/localkube ~/.minikube/cache/localkube/localkube-v1.9.0

kgi-mbp-i7-2:~ kgignatyev$ ls -al ~/.minikube/cache/localkube/localkube-v1.9.0/localkube Display all 190 possibilities? (y or n) kgi-mbp-i7-2:~ kgignatyev$ minikube start Starting local Kubernetes v1.9.0 cluster… Starting VM… Getting VM IP address… Moving files into cluster… E0126 13:42:57.433437 13866 start.go:234] Error updating cluster: Error running scp command: sudo scp -t /usr/local/bin output: scp: Broken pipe : Process exited with status 1

I am having the same issue.

E0126 13:22:42.801521 74141 start.go:234] Error updating cluster: Error updating localkube from uri: Error creating localkube asset from url: Error opening file asset: /Users/brandonbethke/.minikube/cache/localkube/localkube-v1.9.0: open /Users/brandonbethke/.minikube/cache/localkube/localkube-v1.9.0: no such file or directory