Skip to content

Conversation

@lsm5
Copy link
Member

@lsm5 lsm5 commented Nov 17, 2025

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

  • Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
    commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
    the sign-off email address. See CONTRIBUTING.md
    for more information.
  • Referenced issues using Fixes: #00000 in commit message (if applicable)
  • Tests have been added/updated (or no tests are needed)
  • Documentation has been updated (or no documentation changes are needed)
  • All commits pass make validatepr (format/lint checks)
  • Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

None

@openshift-ci openshift-ci bot added release-note-none do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 17, 2025
@lsm5
Copy link
Member Author

lsm5 commented Nov 17, 2025

Depends on containers/container-libs#464

@lsm5 lsm5 added the No New Tests Allow PR to proceed without adding regression tests label Nov 17, 2025
@lsm5 lsm5 force-pushed the cgv1-removal-vendor branch from 64c886a to 2b337bb Compare November 21, 2025 15:50
@github-actions github-actions bot added the kind/api-change Change to remote API; merits scrutiny label Nov 21, 2025
@lsm5 lsm5 changed the title Remove AddPid and simplify cgroups.AvailableControllers CGgroups v1 cleanup: Round 2 w/ container-libs vendoring Nov 21, 2025
@lsm5
Copy link
Member Author

lsm5 commented Nov 21, 2025

machine-linux podman fedora-42-aarch64 rootless host failing with Failed to start: FAILED_PRECONDITION: Insufficient capacity. (Service: Ec2, Status Code: 500, Request ID: 816dcd07-0785-4d68-a143-ddf5eea0d459) (SDK Attempt Count: 4) . Does that usually occur?

_, 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 {
Copy link
Contributor

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.)

Copy link
Member Author

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?

Copy link
Member

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

Copy link
Member Author

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!

@lsm5 lsm5 force-pushed the cgv1-removal-vendor branch 2 times, most recently from df346e1 to c1a613b Compare November 24, 2025 20:05
lsm5 added a commit to lsm5/container-libs that referenced this pull request Nov 25, 2025
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>
@lsm5 lsm5 force-pushed the cgv1-removal-vendor branch 2 times, most recently from b25b3f7 to 059964e Compare November 25, 2025 19:04
@packit-as-a-service
Copy link

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

lsm5 added a commit to lsm5/container-libs that referenced this pull request Dec 2, 2025
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>
@lsm5 lsm5 force-pushed the cgv1-removal-vendor branch from 059964e to cd6d8c1 Compare December 2, 2025 15:42
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 2, 2025
@lsm5 lsm5 force-pushed the cgv1-removal-vendor branch from cd6d8c1 to e525664 Compare December 2, 2025 15:53
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 2, 2025
@packit-as-a-service
Copy link

Cockpit tests failed for commit cd6d8c1. @martinpitt, @jelly, @mvollmer please check.

Also simplifies cgroups.AvailableControllers

Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
@lsm5 lsm5 force-pushed the cgv1-removal-vendor branch from e525664 to b78f1cf Compare December 2, 2025 20:38
@lsm5
Copy link
Member Author

lsm5 commented Dec 2, 2025

vendored container-libs commit df55d6c661e8 in this PR.

Copy link
Contributor

@mtrmac mtrmac left a 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.

@packit-as-a-service
Copy link

Cockpit tests failed for commit b78f1cf. @martinpitt, @jelly, @mvollmer please check.

@lsm5
Copy link
Member Author

lsm5 commented Dec 3, 2025

Cockpit tests are failing on other PRs too, so I think we can ignore them here.

cc @martinpitt

@lsm5 lsm5 marked this pull request as ready for review December 3, 2025 13:50
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 3, 2025
@lsm5
Copy link
Member Author

lsm5 commented Dec 3, 2025

@containers/podman-maintainers PTAL

Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@martinpitt
Copy link
Contributor

@lsm5: wrt. the recent failure:

podman run --log-driver=passthrough --name {container_name} -d {IMG_ALPINE} false </dev/null
fchown std stream 1: Permission denied
Error: crun: fchown std stream 1: Permission denied: OCI permission denied

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?

@openshift-merge-bot openshift-merge-bot bot merged commit 963aabb into containers:main Dec 3, 2025
87 of 88 checks passed
@lsm5 lsm5 deleted the cgv1-removal-vendor branch December 3, 2025 14:07
@lsm5
Copy link
Member Author

lsm5 commented Dec 3, 2025

At least F43 is still green, which for the time being should be enough to verify podman PRs?

I'm cool with that. If anyone finds the failures to be an issue, we could disable the rawhide cockpit jobs.

lsm5 added a commit to lsm5/buildah that referenced this pull request Dec 3, 2025
This vendors container-libs commit `df55d6c661e85a57c0931574373afe6a0259d873`.

Similar Podman PR: containers/podman#27551 .

Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
@Luap99
Copy link
Member

Luap99 commented Dec 3, 2025

@lsm5: wrt. the recent failure:

podman run --log-driver=passthrough --name {container_name} -d {IMG_ALPINE} false </dev/null
fchown std stream 1: Permission denied
Error: crun: fchown std stream 1: Permission denied: OCI permission denied

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?

@giuseppe FYI

@martinpitt
Copy link
Contributor

martinpitt commented Dec 3, 2025

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 denied

It has to go via ssh as the passthrough driver doesn't work in a pty.

  • current fedora-rawhide proper: pass
  • current fefora-rawhide plus podman-next copr: pass (unexpected)
  • current fedora-rawhide image with podman-next and dnf-update: fails
  • only upgrading selinux-policy 42.17-1.fc44 → 42.18-1.fc44 (surprising)
  • fails with openssh 10.0p1-8.fc44 → 10.0p1-9.fc44 ⚡ . Confirmed with stock rawhide without any copr, and only updating that package.

So.. it's not SELinux, and it's not DNS.. That must be a first!

@martinpitt
Copy link
Contributor

So.. it's not SELinux

Sorry, this was wrong after all. It is SELinux. The -9 change is massive is massive and says "Remove redundant SELinux patches", and setenforce 0 makes the test pass.

Not enough bandwidth on the f2f to file an openssh bugzilla, can someone beat me to it?

@martinpitt
Copy link
Contributor

@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.

@martinpitt
Copy link
Contributor

For the record: openssh regression is reported here: https://bugzilla.redhat.com/show_bug.cgi?id=2418587

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/api-change Change to remote API; merits scrutiny lgtm Indicates that a PR is ready to be merged. No New Tests Allow PR to proceed without adding regression tests release-note-none

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants