-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
cgroups v1 isn't supported #2195
Comments
I updated the issue title to better reflect what the problem is |
This is actually a hybrid setup, where both cgroups v1 and v2 are available. Seastar shouldn't fallback to using v1 just because this file has more than single line. It should use memory controller from version in which it's deployed, either v1 or v2. |
@zimnx can you add instructions on how to reproduce this? It's simple to fix but hard to get a reproducing configuration. Maybe it's easiest to enable both v1 and v2 on some kernel and rebuild it, rather than attempt to teach someone how to login to bottlerocket. |
So should the title be "cgroups isn't supported when both v1 and v2 are available"? |
Deploying a single node of bottlerocket on EKS is probably much simpler than preparing the right kernel. And working on same setup where issue was found, would give us more trust.
And create EKS cluster via
Output should contain IP address of a node, if not, it can be extracted via |
If needed I can set it up for you for the time of development. |
Those yamls don't help me, I don't know what to do with them. Also, it's not enough to set up an instance, I want to know how to connect to it, and how to start a non-admin container that I can connect to. |
It's three step guide, it's hard to make it simpler.
Running Pods on Kubernetes is very similar to how you do it using podman. |
On Bottlerocket OS (AWS), memory limit cannot be read by Seastart due to wrong implementation, resulting in no memory limit causing OOMs.
If there's a single line in
/proc/<pid>/cgroup
Seastart uses cgroupv2 logic, but on Bottlerocket there're more lines, so it falls back to cgroupsv1.Seastar shouldn't assume this path contains single line, as manual page https://man7.org/linux/man-pages/man7/cgroups.7.html (search for /proc/pid/cgroup) suggests it may contain more.
Seastart should follow manual guide for this file.
The text was updated successfully, but these errors were encountered: