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

dbuild fails with an error on older kernels (without cgroupsv2) #7938

Closed
avikivity opened this issue Jan 20, 2021 · 2 comments
Closed

dbuild fails with an error on older kernels (without cgroupsv2) #7938

avikivity opened this issue Jan 20, 2021 · 2 comments

Comments

@avikivity
Copy link
Member

$ ./tools/toolchain/dbuild 
Error: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: process_linux.go:422: setting cgroup config for procHooks process caused: cannot set pids limit: container could not join or create cgroup: OCI runtime error
@avikivity
Copy link
Member Author

See containers/podman#6834

avikivity added a commit to avikivity/scylladb that referenced this issue Jan 20, 2021
Podman doesn't correctly support --pids-limit with cgroupsv1. Some
versions ignore it, and some versions reject the option.

To avoid the error, don't supply --pids-limit if cgroupsv2 is not
available (detected by its presence in /proc/filesystems). The user
is required to configure the pids limit in
/etc/containers/containers.conf.

Fixes scylladb#7938.
avikivity added a commit to avikivity/scylladb that referenced this issue Jan 20, 2021
Podman doesn't correctly support --pids-limit with cgroupsv1. Some
versions ignore it, and some versions reject the option.

To avoid the error, don't supply --pids-limit if cgroupsv2 is not
available (detected by its presence in /proc/filesystems). The user
is required to configure the pids limit in
/etc/containers/containers.conf.

Fixes scylladb#7938.
nyh pushed a commit that referenced this issue Jan 20, 2021
Podman doesn't correctly support --pids-limit with cgroupsv1. Some
versions ignore it, and some versions reject the option.

To avoid the error, don't supply --pids-limit if cgroupsv2 is not
available (detected by its presence in /proc/filesystems). The user
is required to configure the pids limit in
/etc/containers/containers.conf.

Fixes #7938.

Closes #7939
syuu1228 pushed a commit to syuu1228/scylla that referenced this issue Jan 25, 2021
Podman doesn't correctly support --pids-limit with cgroupsv1. Some
versions ignore it, and some versions reject the option.

To avoid the error, don't supply --pids-limit if cgroupsv2 is not
available (detected by its presence in /proc/filesystems). The user
is required to configure the pids limit in
/etc/containers/containers.conf.

Fixes scylladb#7938.

Closes scylladb#7939
@avikivity
Copy link
Member Author

Build-only issue, will backport if we hit it in practice.

benipeled pushed a commit to benipeled/scylla that referenced this issue May 31, 2022
Podman doesn't correctly support --pids-limit with cgroupsv1. Some
versions ignore it, and some versions reject the option.

To avoid the error, don't supply --pids-limit if cgroupsv2 is not
available (detected by its presence in /proc/filesystems). The user
is required to configure the pids limit in
/etc/containers/containers.conf.

Fixes scylladb#7938.

Closes scylladb#7939

(cherry picked from commit daa0e96)

Ref scylladb#2008.
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

Successfully merging a pull request may close this issue.

2 participants