container: update real-time resources#33731
Conversation
|
wait, this is still missing containerd changes... |
|
Sorry for the confusion, I had time now to create containerd/containerd#1031 - after that's merged I'll re-vendor containerd here for this PR |
|
@mlaventure @cpuguy83 good to go now |
|
@runcom looks like the default spec generation needs to be updated. |
|
Hopefully fixed |
|
Looks like oom_score_adj is broken now: |
05183be to
4b294ca
Compare
bumped runc to take care of it I guess |
|
alright, runc is still way to old wrt runtime-spec, I'm bumping it again... |
|
looks like spec must be updated in containerd v0.2.x to use new runc.... |
|
ping @runcom |
|
ping @runcom what's the status on this one? Looks like it needs a rebase at least 😅 |
|
ping @runcom what's the status on this pr? needs a rebase |
need to take care of that but it wasn't trivial as many stuff have alerady been updated there...I'll re-work on this asap |
Signed-off-by: Antonio Murdaca <[email protected]>
1e528d2 to
dca82b9
Compare
|
@coolljt0725 @thaJeztah @mlaventure updated |
|
LGTM |
CPU real-time period and runtime are actually sent as part of an update
command via the cli:
https://github.com/docker/cli/blob/master/cli/command/container/update.go#L20-L21
This patch makes update effective because, until now, those settings
weren't actually updated in a container.
Tested in on a real-time kernel, this fixes the issue. Can't add a test
though as I don't think CI has rt kernels enabled.
Reproducer on a rt kernel:
Signed-off-by: Antonio Murdaca [email protected]
- What I did
- How I did it
- How to verify it
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)