Skip to content
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

Open
spowelljr opened this issue Nov 16, 2021 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@spowelljr
Copy link
Member

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.

@spowelljr spowelljr added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/proposal proposals triage/discuss Items for discussion and removed kind/feature Categorizes issue or PR as related to a new feature. labels Nov 16, 2021
@afbjorklund
Copy link
Collaborator

afbjorklund commented Nov 20, 2021

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 du -hs ~/.minikube/cache/*/ ~/.minikube/machines/*/, but probably done in Go ?


338M    /home/anders/.minikube/cache/images/
226M    /home/anders/.minikube/cache/iso/
205M    /home/anders/.minikube/cache/linux/
502M    /home/anders/.minikube/cache/preloaded-tarball/
4,4G    /home/anders/.minikube/machines/minikube/

In my case here, the biggest problem is the "rawdisk" of the libvirt driver. It causes the file to balloon.

Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        17G  1.7G   15G  11% /mnt/vda1

After compaction (qemu-img convert), the file is back to 1.7G again. Other drivers could have similar ?

@afbjorklund
Copy link
Collaborator

afbjorklund commented Nov 20, 2021

There have been some comments by users that they find minikube uses a lot of disk space ...

This is also relative.

Minikube does consume a lot of disk space, compared to previous solutions like docker-machine and localkube.

174M /home/anders/docker-machine-minikube-install/localkube/

784M /home/anders/.docker/machine/machines/default/

But it should consume a comparable amount, when compared to something like vagrant and plain kubeadm ?

A couple of GiB is "expected".


  • The minikube ISO is approximately half (250M), compared to the various ISO for cloud* (500M)

* https://cloud-images.ubuntu.com/focal/current/*.img

  • The minikube binaries (uncompresssed) are something like double, compared to the deb packages.

  • The minikube preload is approximately double (500M), compared to the images tarball* (250M)

* kubeadm config images list | xargs docker save | pigz

  • The minikube preload also includes the size of the storage provisioner and kubernetetes dashboard.

@medyagh
Copy link
Member

medyagh commented Dec 1, 2021

I agree with the fucntionatliy be useful, how about adding a generic command called
that could later add more stuff in addition to disk usage.

"minikube info"

@medyagh medyagh added kind/feature Categorizes issue or PR as related to a new feature. and removed triage/discuss Items for discussion kind/proposal proposals labels Dec 1, 2021
@medyagh
Copy link
Member

medyagh commented Dec 1, 2021

this item is available and I would accept a Pr

@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 1, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 31, 2022
@spowelljr spowelljr added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Apr 6, 2022
@spowelljr spowelljr added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants