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.
Bug 2092798 - podman installation includes runc as a dependency
Summary: podman installation includes runc as a dependency
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: podman
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Joy Pu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-02 09:30 UTC by Suhaas Bhat
Modified: 2022-11-15 10:11 UTC (History)
9 users (show)

Fixed In Version: podman-4.1.0-4.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 09:51:14 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-124039 0 None None None 2022-06-02 09:34:55 UTC
Red Hat Product Errata RHSA-2022:7954 0 None None None 2022-11-15 09:52:21 UTC

Description Suhaas Bhat 2022-06-02 09:30:01 UTC
Description of problem:
Since crun is the default runtime on RHEL 9 podman still ensures that runc is a dependency while installing podman

Version-Release number of selected component (if applicable):
podman-4.x

How reproducible:
Fully

Steps to Reproduce:
# dnf repoquery --requires podman|grep run
Last metadata expiration check: 0:08:46 ago on Fri May 30 22:29:33 2022.
oci-runtime
runc >= 1.0.0-57

Actual results:
Shows runc as a dependency

Expected results:
Remove runc as a dependency

Additional info:
https://github.com/containers/podman/discussions/14307

Comment 1 Jindrich Novy 2022-06-02 09:44:27 UTC
podman-4.1.0-4.el9 patches the spec file like this:

-Requires: runc >= 1.0.0-57
+Recommends: crun

Comment 3 Joy Pu 2022-06-06 12:07:41 UTC
Checked with podman-4.1.0-4.el9.src.rpm and the spec file already updated:
# grep run rpmbuild/SPECS/podman.spec 
Recommends: crun
Requires: oci-runtime
Most %{name} commands can be run as a regular user, without requiring
%{_userunitdir}/*.service
%{_userunitdir}/*.socket
%{_userunitdir}/*.timer
- don't require runc and Recommends: crun
- revert previous change and run `set_build_flags` before the build process
- require oci-runtime to assure either crun or runc is pulled in via
[root@sweetpig-9 ~]# 
So set tested flag.

Comment 7 Joy Pu 2022-06-20 09:00:29 UTC
checked with podman 4.1.1-1.el9 and it works as expected:
#  dnf repoquery --requires podman|grep run
Last metadata expiration check: 0:35:31 ago on Mon 20 Jun 2022 01:51:38 PM IST.
oci-runtime

Comment 9 errata-xmlrpc 2022-11-15 09:51:14 UTC
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 (Moderate: podman security and bug fix 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/RHSA-2022:7954


Note You need to log in before you can comment on or make changes to this bug.