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

Disk usage and memory inconsistency in minikube start #9115

Closed
aps831 opened this issue Aug 29, 2020 · 5 comments
Closed

Disk usage and memory inconsistency in minikube start #9115

aps831 opened this issue Aug 29, 2020 · 5 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. kind/support Categorizes issue or PR as a support question.

Comments

@aps831
Copy link

aps831 commented Aug 29, 2020

minikube version: v1.12.3

The flags for setting disk size and memory have the same usage other than for the default value:

minikube start --help [snipped]
     --disk-size='20000mb': Disk size allocated to the minikube VM (format: <number>[<unit>], where unit = b, k, m or g).   
     --memory='': Amount of RAM to allocate to Kubernetes (format: <number>[<unit>], where unit = b, k, m or g).

Specifying no unit works as expected:

minikube start --driver=virtualbox --memory=8192 --disk-size=8192
[snipped]
Creating virtualbox VM (CPUs=2, Memory=8192MB, Disk=8192MB) ..

Specifying a unit of m works for disk-size only:

minikube start --driver=virtualbox --memory=8192m --disk-size=8192m
[snipped]
Creating virtualbox VM (CPUs=2, Memory=3900MB, Disk=8192MB) ...

Specifying a unit of mb works for disk-size only:

minikube start --driver=virtualbox --memory=8192mb --disk-size=8192mb
[snipped]
Creating virtualbox VM (CPUs=2, Memory=3900MB, Disk=8192MB) ...
@priyawadhwa priyawadhwa added the kind/support Categorizes issue or PR as a support question. label Sep 8, 2020
@priyawadhwa
Copy link

Hey @aps831 thanks for pointing out this inconsistency! If you, or anyone else, would be interested in fixing this, feel free to assign yourself to this issue by commenting /assign.

@priyawadhwa priyawadhwa added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. labels Sep 8, 2020
@Dean-Coakley
Copy link
Contributor

/assign

@Dean-Coakley
Copy link
Contributor

Dean-Coakley commented Sep 8, 2020

@aps831 I'm unable to reproduce this issue, can you try reproduce on minikube 1.13?

@aps831
Copy link
Author

aps831 commented Sep 9, 2020 via email

@aps831
Copy link
Author

aps831 commented Sep 12, 2020

Working on minikube 1.13. Fixed by #9033

@aps831 aps831 closed this as completed Sep 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

3 participants