Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
cgroup.memory.limit returning incorrect value? #85
Comments
|
Hi Henry, This value is extracted directly the kernel via /sys/fs/cgroup/memory/[...]memory.limit_in_bytes ... do you see different values in those files? |
hc000
commented
Apr 14, 2016
•
|
Hi Nathan, It does indeed show match the value. root@slave2:/sys/fs/cgroup/memory/docker/f4a901378ba4ef619091a4ee9c71607eeb81e25ec75bdd66184e147471d95dfe# cat memory.limit_in_bytes && cat memory.usage_in_bytes Memory usage in bytes seems to be correct but not memory limit. I think its related to this issue docker/docker#18087 Is there any metric that gets the values of MemTotal and MemFree from /proc/meminfo ? these looks similar: mem.physmem |
hc000 commentedApr 14, 2016
While doing some testing I noticed this metric is returning the max value of 64-bit unsigned integer.
Tested on a VM with 2GB of ram and a bare metal with 256GB of ram.
Saw this in Version 3.10.9-1 and 3.11.0