Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionZachary Sistrunk
2022-12-28 00:03:15 UTC
Description of problem:
This is a sort of intersection of two separate bugs.
First is https://bugzilla.redhat.com/show_bug.cgi?id=1897579, where enabling cgroupsv2 causes rootless Podman to fail. Fixing it requires enabling Delegation and activating accounting. Doing so allows the rootless Podman to control cgroupsv2 correctly, but also causes systemd to automatically create transient units for Podman containers. This causes the bug described in https://bugzilla.redhat.com/show_bug.cgi?id=2133792 to appear, where containers fail to start due to Unit user-libpod_pod_SHA.slice already exists. This bug was fixed with a later version of systemd, but that version is not yet available in RHEL 8 repositories.
I'm hoping to find a workaround or some additional configuration that can enable us to use rootless Podman without having to wait for the latest systemd update, whether the configuration is in Podman or systemd.
Version-Release number of selected component (if applicable):
systemd-239-58.el8_6.7.x86_64
podman-4.1.1-2.module+el8.6.0+15917+093ca6f8.x86_64
How reproducible:
The same situation has occurred on both of the two systems we currently have Podman installed on
Steps to Reproduce:
1. Enable cgroupsv2
2. Follow the steps in https://access.redhat.com/solutions/6964319
3. Attempt to run any container
Actual results:
Error: OCI runtime error: runc: runc create failed: unable to start container process: unable to apply cgroup configuration: unable to start unit "libpod-f031bbcb680419e81781c9074a5a0f5a39b3a6b7a1c6d87c3540b145dbff471e.scope" (properties [{Name:Description Value:"libcontainer container f031bbcb680419e81781c9074a5a0f5a39b3a6b7a1c6d87c3540b145dbff471e"} {Name:Slice Value:"user.slice"} {Name:Delegate Value:true} {Name:PIDs Value:@au [318889]} {Name:MemoryAccounting Value:true} {Name:CPUAccounting Value:true} {Name:IOAccounting Value:true} {Name:TasksAccounting Value:true} {Name:DefaultDependencies Value:false}]): error creating systemd unit `libpod-f031bbcb680419e81781c9074a5a0f5a39b3a6b7a1c6d87c3540b145dbff471e.scope`: got `failed`
Expected results:
A running container
Additional info:
I previously submitted this on Podman's GitHub. https://github.com/containers/podman/issues/16936
I was able to bypass the error by changing the cgroups manager from systemd to cgroupfs.
Also, I attempted to recreate the initial issue on a local VM that I have root access to. I used the same RHEL version and installed packages as the company VMs and followed the same steps our system admins did, but the container started successfully. The only difference I can think of is that I rebooted my local VM, which I'm not sure if my admins did. I will talk with them and do some more investigation on our side. You can close this ticket for now, although I would appreciate any advice on how I can further investigate if a reboot doesn't work. Thank you!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:7097