stop+start breaks addons: /etc/kubernetes/addons not recreated

[tstromberg]

If you attempt to start a started cluster, we output a warning:

🌟  Enabling addons: default-storageclass, storage-provisioner
⚠️  Enabling 'default-storageclass' returned an error: running callbacks: [sudo test -d /etc/kubernetes/addons && sudo scp -t /etc/kubernetes/addons && sudo touch -d "0001-01-01 00:00:00 +0000" /etc/kubernetes/addons/storageclass.yaml: Process exited with status 1
output: ]
⚠️  Enabling 'storage-provisioner' returned an error: running callbacks: [sudo test -d /etc/kubernetes/addons && sudo scp -t /etc/kubernetes/addons && sudo touch -d "0001-01-01 00:00:00 +0000" /etc/kubernetes/addons/storage-provisioner.yaml: Process exited with status 1

The root cause is unknown.

[tstromberg]

This only happens if you run minikube stop in between. It seems that the new code to call mkdir only once is not executed if the host is recreated.

[limbuu]

i am facing same issue. How to solve this??

[limbuu]

@tstromberg doing sudo minikube start --vm-driver=none solve this issue. But i want to run minikube using Virtual Box as VM. doing minikube start --vm-driver=virtualbox, this issue is also fixed and i can get access to dashboard using minikube dashboard --url but without driver in sudo mode, i cant get access to dashboard. Is it because minikube is running in sudo mode?