-
Notifications
You must be signed in to change notification settings - Fork 363
cgroup: do not create a sub-cgroup by default #1768
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
Open
giuseppe
wants to merge
1
commit into
containers:main
Choose a base branch
from
giuseppe:drop-default-systemd-sub-cgroup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+25
−22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `run.oci.systemd.subgroup` annotation previously defaulted to creating a "container" sub-cgroup on cgroup v2 systems if the annotation was not specified. This change alters the behavior so that no sub-cgroup is created by default. A sub-cgroup will only be created if the `run.oci.systemd.subgroup` annotation is explicitly provided with a non-empty value. Closes: containers#1766 Signed-off-by: Giuseppe Scrivano <[email protected]>
Reviewer's GuideChange default behavior to no longer create a systemd sub-cgroup unless the Class diagram for find_systemd_subgroup function changeclassDiagram
class find_systemd_subgroup {
+string_map *annotations
+returns: const char *
- Old: returns "container" if annotation not set
- New: returns NULL if annotation not set
}
Flow diagram for systemd sub-cgroup creation logicflowchart TD
A[Container start] --> B{Is run.oci.systemd.subgroup annotation set?}
B -- No --> C[No sub-cgroup is created]
B -- Yes, non-empty --> D[Create sub-cgroup with specified name]
B -- Yes, empty --> C
File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
@haircommander FYI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
run.oci.systemd.subgroup
annotation previously defaulted to creating a "container" sub-cgroup on cgroup v2 systems if the annotation was not specified. This change alters the behavior so that no sub-cgroup is created by default.A sub-cgroup will only be created if the
run.oci.systemd.subgroup
annotation is explicitly provided with a non-empty value.Closes: #1766
Summary by Sourcery
Only create a systemd sub-cgroup when the run.oci.systemd.subgroup annotation is explicitly set, removing the previous default of “container” on cgroup v2.
Bug Fixes:
Enhancements: