-
Notifications
You must be signed in to change notification settings - Fork 314
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
OCI runtime error: crun: writing file /sys/fs/cgroup/cgroup.subtree_control
: Invalid argument
#1322
Comments
Please refer to #704 |
Moving this to |
workaround bug containers/crun#1322
workaround bug containers/crun#1322
I am facing the issue on GitHub hosted-runners, I run |
@maxbrunet Could you share the logs here ? I am not sure if the issue you are facing is directly related to crun but logs would help. |
Hey @flouthoc, here is a minimal reproduction: https://github.com/maxbrunet/crun-node20-subtree-control Please feel free to fork it and tinker with it if needed Thank you in advance for your help |
Issue Description
Run container failed on Fedora 37 and 38 with the same error
Error: OCI runtime error: crun: writing file '/sys/fs/cgroup/cgroup.subtree_control': Invalid argument
Fedora 37 test log: https://github.com/virt-s1/rhel-edge/actions/runs/6463309998/job/17546300072#step:4:5427
Fedora 38 test log: https://github.com/virt-s1/rhel-edge/actions/runs/6463310904/job/17546300008#step:4:5577
The debug info:
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Run container with podman failed.
Describe the results you expected
Run container without error
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
aardvark-dns-1.8.0-1.fc38.x86_64
container-selinux-2:2.222.0-1.fc38.noarch
containers-common-4:1-89.fc38.noarch
containers-common-extra-4:1-89.fc38.noarch
crun-1.9.2-1.fc38.x86_64
podman-5:4.7.0-1.fc38.x86_64
podman-plugins-5:4.7.0-1.fc38.x86_64
The text was updated successfully, but these errors were encountered: