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

Insufficient memory / CPU? #567

Closed
aliakhtar opened this issue Sep 12, 2016 · 17 comments

Comments

Projects
None yet
@aliakhtar
Copy link

commented Sep 12, 2016

My laptop has 60+ GB of ram, and a 4-core i7 cpu. But when I try to create a deployment using 1 cpu and 1Gi as the memory / cpu requests, I get told there's insufficient CPU and memory. What gives?

Ubuntu 16.04, virtualbox.

@dlorenc

This comment has been minimized.

Copy link
Contributor

commented Sep 12, 2016

Hey,

The minikube VM is configured by default to only use 1gb of memory. You can pass more during minikube start with the --memory flag. Note that you'll need to stop/start minikube for this to take effect.

@aliakhtar

This comment has been minimized.

Copy link
Author

commented Sep 12, 2016

@dlorenc

This comment has been minimized.

Copy link
Contributor

commented Sep 12, 2016

Same thing, we start with 1 CPU by default. --cpus= will get you more.

@r2d4

This comment has been minimized.

Copy link
Member

commented Sep 12, 2016

You can run minikube start -h to display this helptext

https://github.com/kubernetes/minikube/blob/master/docs/minikube_start.md

@r2d4 r2d4 closed this Sep 13, 2016

@aliakhtar

This comment has been minimized.

Copy link
Author

commented Sep 15, 2016

I'm 'guessing' that the memory is is specified in Mb but it would be useful to have that listed more clearly in the help text

@giorgiosironi

This comment has been minimized.

Copy link

commented Jan 29, 2017

Running:

minikube stop && minikube start --cpus 4 --memory 8192

in Minikube v0.14.0 does not change the capacity of kubectl describe nodes, which stays at cpu: 2, the current default. Maybe there is something else to recreate too?

@uschmann

This comment has been minimized.

Copy link

commented Mar 3, 2017

minikube start --memory 4096
Does not increase the memory for my machine.

I am on a mac using virtualbox as a virtualisation-driver.

If i take a look in the virtualbox settings of the VM i can see that memory is still at 2gb.

Any idea?

@aaron-prindle

This comment has been minimized.

Copy link
Contributor

commented Mar 3, 2017

@uschmann Was a minikube VM already running? If there is already a minikube VM running, the memory won't be changed as this is done on creation of the VM. You will have to run a minikube delete; minikube start --memory 4096 to have the increased memory. We have an issue tracking this here: #1147

@gsccheng

This comment has been minimized.

Copy link

commented Mar 17, 2017

@uschmann or to set as default you can do something like this and restart Minikube:
minikube config set memory <memory>

@easternbloc

This comment has been minimized.

Copy link

commented Jun 2, 2017

You do indeed have to delete before any edited config is reflected 😞

@dturanski

This comment has been minimized.

Copy link

commented Oct 14, 2017

On OS/X Virtualbox, I found the minikube memory setting was having no effect. I had to change it in VB.

@skhatri

This comment has been minimized.

Copy link

commented Jan 15, 2018

I did this on my mac

minikube stop
minikube delete
minikube --memory 8192 --cpus 2 start
@PavelSosin

This comment has been minimized.

Copy link

commented Jul 10, 2018

Finally, I had to delete entire minikube cluster to enlarge my minikube node to accommodate more Eclipse Che workspaces. Fortunately, it was only results of investigations but I spent few days to accumulate these results. Could you propose another way to manage minikube node size, even, via re-configuration of Oracle V-Box VM manually?

@losymear

This comment has been minimized.

Copy link

commented Sep 6, 2018

If you are using VirtualBox, you can first change the momory for that vm , then reconfig and restart. Look at this.

@alecholmez

This comment has been minimized.

Copy link

commented Nov 19, 2018

I used:

minikube config set memory 8192
minikube config set cpus 2

Seemed to persist my changes as well

@IvanBoyko

This comment has been minimized.

Copy link

commented Feb 6, 2019

Yes, it saves new values in config file:

$ cat ~/.minikube/config/config.json 
{
    "cpus": 4,
    "dashboard": true,
    "memory": 4096
}

@muratzorer

This comment has been minimized.

Copy link

commented Apr 8, 2019

You dont have to delete minikube vm just to reconfigure some specs. Use the cli command of your hypervisor to reconfigure. For virtualbox:

$ minikube stop
$ VBoxManage modifyvm "minikube" --cpus 4 --memory 8196
$ minikube start --memory=8196 --cpus=4 --kubernetes-version=v1.13.0 \
    --vm-driver=virtualbox

Either way there is still a problem with minikube (v1.0.0), we cannot reconfigure --cpu for virtualbox (v5.2.24)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.