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

minikube 1.12.3 fails to interpret memory unit correctly #9057

Closed
rkialashaki opened this issue Aug 21, 2020 · 2 comments
Closed

minikube 1.12.3 fails to interpret memory unit correctly #9057

rkialashaki opened this issue Aug 21, 2020 · 2 comments
Labels
triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@rkialashaki
Copy link

Steps to reproduce the issue:

  1. Mac OSX Catalina 10.15.5
  2. Docker Desktop for Mac 2.3.0.4
  3. brew install minikube
  4. From minikube help:
--memory='': Amount of RAM to allocate to Kubernetes (format: <number>[<unit>], where unit = b, k, m or g).
  1. minikube start --cpus 6 --memory 16g

Notice I specify the memory allocation for the minikube container should be 16GB, however, in the output below, you will see minikube creates a docker container of memory 8100MB instead.

Full output of failed command:

😄  minikube v1.12.3 on Darwin 10.15.5
✨  Automatically selected the docker driver. Other choices: hyperkit, virtualbox
👍  Starting control plane node minikube in cluster minikube
🔥  Creating docker container (CPUs=6, Memory=8100MB) ..

Full output of minikube start command used, if not already included:

Optional: Full output of minikube logs command:

@unixlab
Copy link

unixlab commented Aug 25, 2020

I think this is a duplicate of #9017 and already fixed in PR #9033.

So I would assume that we just need to wait until the fix get released in a 1.12.4 bug fix release or wait for 1.13.0

@sharifelgamal
Copy link
Collaborator

Correct, this will be fixed with our 1.13.0 release which should be out soon. Sorry for the bad experience here. I'll close this as a dupe.

@sharifelgamal sharifelgamal added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Aug 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

3 participants