Hi @HarHarLinks, thanks for reporting this issue, while this is far from a normal use case I agree that we can easily implement a size check to not show errors if space is greater than XGB. Also, I think we should take the --force flag into consideration so someone can completely bypass the check if they want.

@spowelljr I'd like to work on this issue if possible. Since I'm a new contributor to this project, would it perhaps be possible to point out some of the code/files I should have a look at?

Hi @F1ko, to assign the issue to yourself comment /assign.

Here's the link to the function where the errors are thrown: https://github.com/kubernetes/minikube/blob/master/pkg/minikube/machine/start.go#L212.

A good number to check for is 20GB, so if the user has less than 85% or 99% space available but greater than 20GB then don't throw any errors or warnings. We should also check if the --force flag is passed and if it is don't do these checks at all, example:

And one last thing is in the error messages, we should notify the user that if they can pass the --force to skip the check if they want to.

Thanks a lot @spowelljr !

/assign

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

going to remove the frozen lifecycle since there are new commits being pushed to the PR

unless there is another reason to freeze this issue? (@spowelljr )

/remove-lifecycle frozen

Frozen prevents it from going stale

Has this issue been worked on? I will like to take it up.

Yes, it actually is done already, I am just waiting for a final review.

Anything I need to do in that regard or just wait @spowelljr ?