-
Notifications
You must be signed in to change notification settings - Fork 2.9k
CGgroups v1 cleanup: Round 2 w/ container-libs vendoring #27551
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
Conversation
|
Depends on containers/container-libs#464 |
64c886a to
2b337bb
Compare
|
|
2b337bb to
7da1bc6
Compare
| _, err := cgroups.New(cgroupPath, &cgroupResources) | ||
| if err != nil { | ||
| logrus.StandardLogger().Logf(logLevel, "Failed to add conmon to cgroupfs sandbox cgroup: %v", err) | ||
| } else if err := control.AddPid(cmd.Process.Pid); err != nil { |
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.
Is removing this correct? (I have no idea.)
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.
@containers/podman-maintainers wdyt? This is only in the case when cgroups manager isn't systemd which (IIRC) is safe to remove. Also, no tests failed with this removal fwiw. So if it is needed at all, do we need a test for this case too?
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.
no, we still support cgroupfs. We need this call to move the process to the target cgroup
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.
ack, got it. I'll revise. Thanks!
df346e1 to
c1a613b
Compare
This reverts commit cce5ec8. Note: This has already gone through a revert and re-revert cycle in commits 5273685 and 3fe402b, but that's wrong per: containers/podman#27551 (comment) . Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
b25b3f7 to
059964e
Compare
|
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
This reverts commit cce5ec8 and calls .Apply to honor the API. Note: This has already gone through a revert and re-revert cycle in commits 5273685 and 3fe402b, but that's wrong per: containers/podman#27551 (comment) . Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
059964e to
cd6d8c1
Compare
cd6d8c1 to
e525664
Compare
|
Cockpit tests failed for commit cd6d8c1. @martinpitt, @jelly, @mvollmer please check. |
Also simplifies cgroups.AvailableControllers Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
e525664 to
b78f1cf
Compare
|
vendored container-libs commit |
mtrmac
left a comment
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.
LGTM if tests pass, given that containers/container-libs#464 was approved by experts.
|
Cockpit tests failed for commit b78f1cf. @martinpitt, @jelly, @mvollmer please check. |
|
Cockpit tests are failing on other PRs too, so I think we can ignore them here. cc @martinpitt |
|
@containers/podman-maintainers PTAL |
Luap99
left a comment
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.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5, Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@lsm5: wrt. the recent failure:
Ah, seems this spontaneously combusted in Rawhide a few days ago. Sorry, in a face-to-face meeting this week with near-zero computer time. Unless this already rings a bell with you, feel free to ignore this week. Next monday I can turn this into a standalone reproducer and file a podman (or crun?) issue. At least F43 is still green, which for the time being should be enough to verify podman PRs? |
963aabb
into
containers:main
I'm cool with that. If anyone finds the failures to be an issue, we could disable the rawhide cockpit jobs. |
This vendors container-libs commit `df55d6c661e85a57c0931574373afe6a0259d873`. Similar Podman PR: containers/podman#27551 . Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
@giuseppe FYI |
|
Observations (mostly my own notes, sorry). Reproducer: $ ssh myrawhidemachine podman run --log-driver=passthrough --rm --name test1 docker.io/alpine false
Warning: Permanently added '[127.0.0.2]:2201' (ED25519) to the list of known hosts.
fchown std stream `0`: Permission denied
Error: crun: fchown std stream `0`: Permission denied: OCI permission deniedIt has to go via ssh as the
So.. it's not SELinux, and it's not DNS.. That must be a first! |
Sorry, this was wrong after all. It is SELinux. The -9 change is massive is massive and says "Remove redundant SELinux patches", and Not enough bandwidth on the f2f to file an openssh bugzilla, can someone beat me to it? |
|
@jelly sent cockpit-project/bots#8507 to mark this as a known failure, to put an end to the massive noise in podman PRs. I'll send the Fedora bug report on Friday when I travel back from the f2f meeting. |
|
For the record: openssh regression is reported here: https://bugzilla.redhat.com/show_bug.cgi?id=2418587 |
Checklist
Ensure you have completed the following checklist for your pull request to be reviewed:
commits. (
git commit -s). (If needed, usegit commit -s --amend). The author email must matchthe sign-off email address. See CONTRIBUTING.md
for more information.
Fixes: #00000in commit message (if applicable)make validatepr(format/lint checks)Noneif no user-facing changes)Does this PR introduce a user-facing change?