-
Notifications
You must be signed in to change notification settings - Fork 110
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
Memory allocation uses the wrong unit for allocation #54
Comments
Build log and artifact:
2 000 000 KiB = 2048 MB |
@r2d4 @aaron-prindle Hi guys, this also affects you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
In the driver plugin actually
M
is being used as the unit for Memory:https://github.com/dhiltgen/docker-machine-kvm/blob/master/kvm.go#L37
And according to the description, this is meant to mean Megabytes:
https://github.com/dhiltgen/docker-machine-kvm/blob/master/kvm.go#L104
However, according to the libvirt documentation
M
is Mebibyteshttps://libvirt.org/formatdomain.html#elementsMemoryAllocation
Solution
In the template
MB
should be used instead to allocate the correct amount of memoryDetails
Currently, in
docker-machine
,minikube
andminishift
, we assign2048
as a default for the memory. This will be treated as MB, and this should result in 2G of memory.However, in
virt-manager
this VM is created with:This means that the VM is actually created with more memory assigned:
2 097 152 KiB = 2.14748365 GB
Ref
Note: this is for all the clients used
docker-machine
,minikube
andminishift
.The text was updated successfully, but these errors were encountered: