-
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
runc update will clear cpu burst value #4210
Comments
I'll add a testcase for this issue later. |
In issue opencontainers#4210, if we don't privide `--cpu-burst` in `runc update`, the value of cpu burst will always set to 0. Signed-off-by: lifubang <[email protected]>
In issue opencontainers#4210, if we don't privide `--cpu-burst` in `runc update`, the value of cpu burst will always set to 0. Signed-off-by: lifubang <[email protected]>
In issue opencontainers#4210, if we don't privide `--cpu-burst` in `runc update`, the value of cpu burst will always set to 0. Signed-off-by: lifubang <[email protected]>
The ubuntu issue you mention seems the same that breaks containerd tests with the new runc: https://github.com/containerd/containerd/actions/runs/8540558806/job/23398018642?pr=9313:
@lifubang do you know already what the fix should/might look like? Or did you find a wall as @kolyshkin with his PR? |
Yes, it’s easy to fix this issue, but we found some other issues for ‘runc update’, we want to fix all of these issues in one PR, but it’s too difficult, I think maybe we should fix them step by step. |
In issue opencontainers#4210, if we don't provide `--cpu-burst` in `runc update`, the value of cpu burst will always set to 0. Signed-off-by: lifubang <[email protected]>
When I'm testing tests/int: swap-related fixes #4188 in ubuntu 20.04 with cgroupv2, I got some errors:
The text was updated successfully, but these errors were encountered: