minikube: Using local driver gets error 'localkube-v1.9.4: no such file or directory'
BUG REPORT
Minikube version v0.25.1:
- OS Ubuntu 17.10:
- VM Driver (none):
- ISO version None (
cat ~/.minikube/machines/minikube/config.json | grep -i ISOproduced no result):
What happened:
Starting local Kubernetes v1.9.4 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
E0322 12:18:47.974752 10867 start.go:234] Error updating cluster: Error updating localkube from uri: Error creating localkube asset from url: Error opening file asset: /home/jackson/.minikube/cache/localkube/localkube-v1.9.4: open /home/jackson/.minikube/cache/localkube/localkube-v1.9.4: no such file or directory
What you expected to happen:
Minikube to start successfully with local driver
How to reproduce it (as minimally and precisely as possible):
Run the Example with kubectl installation in README.md:
curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && chmod +x minikube
curl -Lo kubectl https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl && chmod +x kubectl
export MINIKUBE_WANTUPDATENOTIFICATION=false
export MINIKUBE_WANTREPORTERRORPROMPT=false
export MINIKUBE_HOME=$HOME
export CHANGE_MINIKUBE_NONE_USER=true
mkdir $HOME/.kube || true
touch $HOME/.kube/config
export KUBECONFIG=$HOME/.kube/config
sudo -E ./minikube start --vm-driver=none
# this for loop waits until kubectl can access the api server that Minikube has created
for i in {1..150}; do # timeout for 5 minutes
./kubectl get po &> /dev/null
if [ $? -ne 1 ]; then
break
fi
sleep 2
done
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 4
- Comments: 17 (5 by maintainers)
workaround I just took. download files and rename to localkube-1.9.4
https://github.com/kubernetes/minikube/releases *localkube *localkube.sha256
then copy to /home/jackson/.minikube/cache/localkube/
This should be fixed now, sorry for the issues. We opened #2632 to help prevent this in the future.
@pgoodjohn The workaround suggested by @cyron above worked for me on MacOS. Just had to rename the two files to
localkube-v1.9.4andlocalkube-v1.9.4.sha256(instead of localkube-1.9.4)