Skip to content
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

not on Raspberry Pi: "memory is chosen randomly, any cgroup used by docker works" #44

Open
thediveo opened this issue Sep 14, 2020 · 3 comments

Comments

@thediveo
Copy link

issue severity: fun fact 😀

// memory is chosen randomly, any cgroup used by docker works

...unfortunately memory cgroup controllers are often disabled on various Raspberry Pi Linux distributions, such as Ubuntu 19.04-20.04. A better bet thus seems to be using another controller type, such as cpu.

@imilchev
Copy link
Contributor

imilchev commented Dec 30, 2020

Be aware that Docker often specifies the cgroup as cpu,cpuacct and if you try using the cpu cgroup it will not find it because of this split

for _, opt := range strings.Split(parts[3], ",") {

I encountered that issue myself. The same applies for net_cls which is mentioned in Docker as net_cls,net_prio

@jeffwidman
Copy link
Collaborator

PR's improving docs, comments, or code are always welcome!

@thediveo
Copy link
Author

Well, I don't think that there much value in trying to fix this particular function: it'll break soon again due to systemd changing cgroup paths anyway. Now, I'm surely opinionated here, as I'm the author of the lxkns discovery engine that for some time now has direct support for relating namespaces and processes to containers by talking to container engines, namely docker, containerd and even podman.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants