The following is a bug.
Environment:
Minikube version (use minikube version): v0.24.1
cat ~/.minikube/machines/minikube/config.json | grep DriverName): hyperkitcat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): minikube-v0.23.6.isoWhat happened: When running minikube start --vm-driver=hyperkit, I get an error saying:
E0115 15:29:12.531514 44736 start.go:156] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: making disk image: truncate /Users/pdoustdar/.minikube/machines/minikube/minikube.rawdisk: no space left on device
What you expected to happen: I expected the machine to be created and provisioned successfully.
How to reproduce it (as minimally and precisely as possible):
minikube start --vm-driver=hyperkit.no space left on device
@parhamdoustdar can you verify how much free disk space you have?
Yes, sure!
I have 28.9 GB free.
I think minikube attempts to reserve 64 GB of disk, so 28.9 GB free might indeed cause the "no space left on device" error.
Can you try running minikube start --vm-driver=hyperkit --disk-size=10g? (choose a number that's less than 28.9 GB here)
Thanks, that worked. I thought the error was not talking about my actual disk, and talking about the VM disk.
Thanks a lot for the quick replies.
Would be nice to have a more descriptive error message, saying "Cannot allocate a 64 disk".
Most helpful comment
Would be nice to have a more descriptive error message, saying "Cannot allocate a 64 disk".