Minikube on Windows 10 using Hyper-V not respecting memory allocation set in profile. #7144
Labels
kind/support
Categorizes issue or PR as a support question.
triage/needs-information
Indicates an issue needs more information in order to work on it.
Comments
|
Yup ... seeing the same thing. Came in here to report the same bug. Same setup as original reporter. |
priyawadhwa
added
kind/bug
|
Hey @DotNet-Ninja @Larswa -- I merged #7082 which should fix this bug. It was released in v1.9.0-beta.1 Would you mind upgrading to any version of minikube >= v1.9.0-beta.1 and seeing if that resolves this issue? |
|
Hi @priyawadhwa I can confirm that works. Thanks! |
|
Great, I'll go ahead and close this issue then. |
|
I can also confirm that does seem to fix the issue. Thanks! |
|
This problem still occurs in minikube 1.12.3. I've downgraded to 1.12.0 which seems to help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been running a set of PowerShell scripts (in various forms) to install and configure Minikube since mid November (starting with ~v1.5.1 if I remember correctly). The gist of the current scripts is there is one to install Minikube using the Chocolatey package and one to configure Minikube and start it up. Last night I began an exercise to clean up the scripts and retest them at which time I noticed that the setting for memory did not seem to be getting applied as expected.
Knowing that this had been working for the previous few months, I went back and verified I had not changed anything that was causing the issue and not seeing anything I looked at the recent release notes to see what had been changed and if possibly the API for setting this was changed. In reviewing the release notes I found that there was a reference to a PR (#6900) that if I understand correctly the intent was to set the memory to 1/4 of the available memory up to 6GB, but never less than 2GB by default (I assume by default means if memory size is not specified?). Interestingly 6GB is exactly what I am seeing allocated even though I'm requesting 8GB (I have 32GB of RAM).
Here is the configuration script I'm using on a clean (brand new install) of Minikube. (In between installs I'm uninstalling Minikube, removing the VM, and deleting the ~.minikube folder on my machine.)
After running that command on the latest version here is my config:
and here is the result of Get-VM on my machine:
I've run my process 3 times this morning since finding the release notes and PR and have verified that this is new to v1.8.2. Below is a copy of the output from running my configuration script all three times:
Minikube Version 1.7.3
Minikube Version 1.8.1
Minikube version 1.8.2
I also tried stopping and restarting Minikube after the configuration script has run to see if that would cause it to pick up the allocated memory and it did not.
I'm wondering if there is an unintentional "bug" causing it to only allocate 6GB in this scenario or if this was by design? If by design, how would I go about allocating more memory?
The exact command to reproduce the issue:
The full output of the command that failed:
The output of the
minikube logscommand:minikube.v1.8.2.logs.txt
I'm also attaching my script files I used.
ConfigureMinikube.zip
The operating system version:
Window 10 Professional Version 1909 build 18363.720
The text was updated successfully, but these errors were encountered: