minikube: ln: failed to create symbolic link '/var/lib/minikube/etcd/minikube': File exists
Subsequent error on minikube restart:
minikube v1.4.0 on Darwin 10.14.3
π‘ Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
π Using the running virtualbox "minikube" VM ...
β Waiting for the host to be provisioned ...
π³ Preparing Kubernetes v1.16.0 on Docker 18.09.8 ...
π Relaunching Kubernetes using kubeadm ...
E0920 14:15:18.905571 77264 kubeadm.go:415] failed to create compat symlinks: cmd failed: sudo ln -s /data/minikube /var/lib/minikube/etcd
ln: failed to create symbolic link '/var/lib/minikube/etcd/minikube': File exists
: Process exited with status 1
_Originally posted by @vsethi in https://github.com/kubernetes/minikube/issues/5415#issuecomment-533848677_
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 4
- Comments: 15 (4 by maintainers)
@seancarroll @dbamaster I am curious, does this issue happen consistently or only happens sometimes ?
if this issue is still happening for you, I wonder if deleting the ISO cache would solve your problem ?
rm ~/.minikube/cache/iso/*or if
minikube deleteand starting it fresh would solve the problem ?This didnt helped in my case. However
minikube deletedid work. π@dbamaster what about temporary downgrading and doing:
kubectl get deployment FOO -o yaml > my-deployment-foo.ymlto save your deploymentsInteresting. As far as I knew, this issue should only happen on existing VMβs with older ISOβs, so
minikube deleteshould have solved the issue.