cgroup2: exec: join the cgroup of the init process on EBUSY#2416
cgroup2: exec: join the cgroup of the init process on EBUSY#2416mrunalp merged 1 commit intoopencontainers:masterfrom
Conversation
AkihiroSuda
force-pushed
the
exec-join-init-cgroup
branch
4 times, most recently
from
e93631c to
dc133ec
Compare
AkihiroSuda
force-pushed
the
exec-join-init-cgroup
branch
2 times, most recently
from
4ece281 to
9643a87
Compare
|
@kolyshkin @cyphar @giuseppe PTAL |
| // On cgroup v2 + nesting + domain controllers, EnterPid may fail with EBUSY. | ||
| // https://github.com/opencontainers/runc/issues/2356#issuecomment-621277643 | ||
| // Try to join the cgroup of InitProcessPid. | ||
| if cgroups.IsCgroup2UnifiedMode() { |
There was a problem hiding this comment.
should it not be done only with err == EBUSY?
There was a problem hiding this comment.
I guess it is worth trying to join pid1 even on other errors
There was a problem hiding this comment.
@AkihiroSuda this decision (try to join pid1 on every error) can be problematic.
I've seen case (in #4812 (comment)) in which the container init is moved to an entirely different cgroup (I'm not sure by whom, but suspect it's some GHA CI infra software). Once this happens, the container's limits, as configured in OCI spec, are no longer applied. Next, we call runc exec and it succeeds (thanks to the patch in this PR), but I'd rather have it failed, because something very bad has happened.
There was a problem hiding this comment.
I also somewhat question this idea in the first place -- administrative cgroup moves are generally not blocked by the cgroup infrastructure (this is an explicit design goal). I think you would only get this case with frozen cgroups, in which case an error is kind of reasonable IMHO?
|
@kolyshkin @mrunalp PTAL |
|
Added one comment about removing the warning otherwise looks ready to merge. Thanks! |
AkihiroSuda
force-pushed
the
exec-join-init-cgroup
branch
from
9643a87 to
5099176
Compare
|
updated |
|
Thanks, will tag once tests pass again. |
|
LGTM |
|
@kolyshkin @cyphar ptal |
AkihiroSuda
force-pushed
the
exec-join-init-cgroup
branch
from
5099176 to
b502a4b
Compare
kolyshkin
left a comment
kolyshkin
left a comment
There was a problem hiding this comment.
a nit with whitespace, but LGTM overall
Signed-off-by: Akihiro Suda <[email protected]>
AkihiroSuda
force-pushed
the
exec-join-init-cgroup
branch
from
b502a4b to
c91fe9a
Compare
|
fixed |
5 participants
Fix #2356.
Contains #2418Note: this behavior is different from crun v0.13.
crun joins "crun-exec` group rather than the init group: containers/crun@af1080b
The next version of crun will switch to the init cgroup: containers/crun#365