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:
Run podman command on CentOS Stream 8 failed with error:
podman: symbol lookup error: podman: undefined symbol: seccomp_notify_fd
Version-Release number of selected component (if applicable):
podman-2:4.0.2-1.module_el8.7.0+1106+45480ee0.x86_64
runc-1.0.2-1.module_el8.6.0+926+8bef8ae7.x86_64
container-selinux-2:2.180.0-1.module_el8.7.0+1106+45480ee0.noarch
containernetworking-plugins-1:1.1.1-1.module_el8.7.0+1106+45480ee0.x86_64
containers-common-2:1-23.module_el8.7.0+1106+45480ee0.x86_64
How reproducible:
Steps to Reproduce:
1. Run "sudo podman network inspect edge" on CentOS Stream 8
Actual results:
Failed with error: podman: symbol lookup error: podman: undefined symbol: seccomp_notify_fd
Expected results:
Run command successfully without error.
Additional info:
No this issue on RHEL 8.6.
No this issue on CentOS Stream 8 with the following podman and its dependencies:
podman-1:3.4.1-3.module_el8.6.0+954+963caf36.x86_64
runc-1.0.2-1.module_el8.6.0+926+8bef8ae7.x86_64
container-selinux-2:2.170.0-1.module_el8.6.0+954+963caf36.noarch
containernetworking-plugins-1.0.1-1.module_el8.6.0+944+d413f95e.x86_64
containers-common-2:1-6.module_el8.6.0+954+963caf36.noarch
I ran into the same issue on the official AWS CentOS Stream 8 image:
libseccomp-2.4.3-1.el8.x86_64
podman-4.0.2-1.module_el8.7.0+1106+45480ee0.x86_64
Upgrading to libseccomp-2.5.2-1.el8.x86_64 fixed the issue. I think you need to put a dependency in podman (or some other package) to explicitly require newer libseccomp.
Xiaofeng, you mention in comment #5 you use CentOS Stream 9 but the libseccomp version mentioned is a RHEL8 version?
Ondrej, I added the libseccomp >= 2.5 requirement to podman - it should appear in c8s tomorrow.
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 (Important: 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:1762