-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Proposal] Include env var to disable kernel memory accounting when kernel <= 3.10 #1898
Comments
This comment has been minimized.
This comment has been minimized.
Sorry, I misunderstood what the issue was (it's been a while since the last The wish for an environment variable or a flag makes some more sense now, but I'm still not really thrilled about it (we added From (2-year-old) memory, the reason why we always enable tl;dr: Not sure what the best way forward is... |
@rhvgoyal WDYT? |
Ya, lets not use flags or env vars to resolve this issue. |
Alternative proposal, checking if the kernel is a one from RHEL7: #1920 |
Closed in favor of #1921 |
When using RedHat or CentOS, base kernel is 3.10 (with some backport and CONFIG_MEMCG_KMEM..).
We encounter on my current project the same error as described is attached issues.
To avoid reboot all ours nodes in production every week (or recompile kernel on every update) we propose to disable it with an env var
DISABLE_KERNEL_MEMORY_ACCOUNTING
inlibcontainer/cgroups/fs/memory.go
.See: https://github.com/ryarnyah/runc/tree/1898-add-optional-kernel-accounting
See: scality/kubernetes@b04b050
See: kubernetes/kubernetes#61937
See: #1350
See: moby/moby#29638
The text was updated successfully, but these errors were encountered: