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.
Description of problem:
Runc fails when libseccomp < 2.5 is installed on a system, such as when installing runc onto a RHEL 8.3 host which already has libseccomp 2.4 installed.
Version-Release number of selected component (if applicable):
runc-3:1.1.0-1.rhaos4.10.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Provision a RHEL 8.3 host, ensure libseccomp 2.4 is installed
2. Install runc-3:1.1.0-1.rhaos4.10.el8.x86_64, podman and friends
3. podman run --rm registry.build03.ci.openshift.org/ci-op-g2j85snf/release@sha256:03540f6edcc4d35c8880ae92cc592cdbdd927f3d767c241f9986dc0908d05ac3 image machine-config-operator
Actual results:
"/usr/bin/runc: symbol lookup error: /usr/bin/runc: undefined symbol: seccomp_notify_respond",
"time=\"2022-02-10T18:43:20Z\" level=error msg=\"Error removing container fb63b3897f8c9ba0ccb7dc24a70d869ed7a8ffb875686f92720f160a79902fe5 from runtime after creation failed\"",
"Error: OCI runtime error: /usr/bin/runc: symbol lookup error: /usr/bin/runc: undefined symbol: seccomp_notify_respond"
Expected results:
Successful container running
Additional info:
It seems seccomp_notify_respond was added in 2.5, I'd expect the rpm to depend on libseccomp >= 2.5 to avoid this issue.
[root@kvm-08-guest11 ~]# rpm -q libseccomp
libseccomp-2.4.3-1.el8.x86_64
[root@kvm-08-guest11 ~]# yum install http://XXX/rhel-8/packages/runc/1.0.3/3.module+el8.7.0+14440+ed5f482d/x86_64/runc-1.0.3-3.module+el8.7.0+14440+ed5f482d.x86_64.rpm
Updating Subscription Management repositories.
Unable to read consumer identity
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Last metadata expiration check: 2:58:54 ago on Tue 15 Mar 2022 02:56:41 AM EDT.
runc-1.0.3-3.module+el8.7.0+14440+ed5f482d.x86_64.rpm 16 MB/s | 3.0 MB 00:00
Error:
Problem: conflicting requests
- nothing provides libseccomp >= 2.5 needed by runc-1:1.0.3-3.module+el8.7.0+14440+ed5f482d.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
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: container-tools:rhel8 security, 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/RHSA-2022:7457