-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement a minikube disk-usage
command so users can see how much space minikube is using
#12967
Comments
Related to: But (also) needs to show the host disk usage, since it can vary greatly (GB) to what the VM is seeing... Something similar to
In my case here, the biggest problem is the "rawdisk" of the libvirt driver. It causes the file to balloon.
After compaction ( |
This is also relative. Minikube does consume a lot of disk space, compared to previous solutions like docker-machine and localkube.
But it should consume a comparable amount, when compared to something like vagrant and plain A couple of GiB is "expected".
*
*
|
I agree with the fucntionatliy be useful, how about adding a generic command called "minikube info" |
this item is available and I would accept a Pr |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
There have been some comments by users that they find minikube uses a lot of disk space and there's no easy way to see how much it's using.
We should implement a command so users can easily view the disk space usage. This will include things like preloads and image caching and output the usage categorically.
The text was updated successfully, but these errors were encountered: