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.

Sign up for GitHub

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

Jump to bottom

minikube start --memory flag is broken in v1.12.3 #9017

Closed
mangoleaf opened this issue Aug 18, 2020 · 1 comment · Fixed by #9033
Closed

minikube start --memory flag is broken in v1.12.3 #9017

mangoleaf opened this issue Aug 18, 2020 · 1 comment · Fixed by #9033
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/regression Categorizes issue or PR as related to a regression from a prior release. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.13.0

Comments

@mangoleaf
Copy link

mangoleaf commented Aug 18, 2020 •
edited
Loading

Steps to reproduce the issue:

Run a command which sets a custom memory amount for the cluster with minikube start

minikube start --driver=virtualbox --cpus=6 --memory=15g --disk-size=50g

Full output of failed command:

😄 minikube v1.12.3 on Fedora 32
✨ Using the virtualbox driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🔥 Creating virtualbox VM (CPUs=6, Memory=6000MB, Disk=51200MB) ...
🐳 Preparing Kubernetes v1.18.3 on Docker 19.03.12 ...
🔎 Verifying Kubernetes components...
🌟 Enabled addons: default-storageclass, storage-provisioner
🏄 Done! kubectl is now configured to use "minikube"

The memory flag in minikube start is ignored and defaults to 6gb. Note the Memory=6000MB in the command output. This command worked as expected in v1.12.0. I recently updated to v1.12.3

Note: I also tried --memory='15g' and obtained the same output.
@prasadkatti prasadkatti added the kind/bug Categorizes issue or PR as related to a bug. label Aug 18, 2020
@vixus0
Copy link
Contributor

vixus0 commented Aug 19, 2020

Experiencing the same issue. For me, it defaults to 3900MB.

@vixus0 vixus0 mentioned this issue Aug 19, 2020
Merged
@tstromberg tstromberg added kind/regression Categorizes issue or PR as related to a regression from a prior release. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 19, 2020
@tstromberg tstromberg added this to the v1.13.0 milestone Aug 19, 2020
@unixlab unixlab mentioned this issue Aug 25, 2020
Closed
@saruman9 saruman9 mentioned this issue Apr 7, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/regression Categorizes issue or PR as related to a regression from a prior release. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.13.0
Development

Successfully merging a pull request may close this issue.

Fix --memory flag parsing in minikube start
4 participants
@tstromberg @vixus0 @mangoleaf @prasadkatti