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 2065292 - CentOS Stream 8 podman: symbol lookup error: podman: undefined symbol: seccomp_notify_fd
Summary: CentOS Stream 8 podman: symbol lookup error: podman: undefined symbol: seccom...
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2022-04-04
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Joy Pu
URL:
Whiteboard:
Depends On:
Blocks: 2068006
TreeView+ depends on / blocked
 
Reported: 2022-03-17 15:34 UTC by Xiaofeng Wang
Modified: 2022-05-10 13:47 UTC (History)
12 users (show)

Fixed In Version: podman-4.0.2-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2068006 (view as bug list)
Environment:
Last Closed: 2022-05-10 13:28:28 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-115971 0 None None None 2022-03-17 15:49:07 UTC
Red Hat Product Errata RHSA-2022:1762 0 None None None 2022-05-10 13:29:20 UTC

Description Xiaofeng Wang 2022-03-17 15:34:54 UTC 
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
Comment 3 Jindrich Novy 2022-03-17 16:38:43 UTC 
Looking at https://github.com/containers/youki/issues/608 - what is the version of libseccomp installed on your system?
Comment 4 Tom Sweeney 2022-03-17 19:47:17 UTC 
@mheon Any thoughts on this one?
Comment 5 Xiaofeng Wang 2022-03-18 00:53:40 UTC 
My CS9 system is using libseccomp-2.5.2-1.el8.x86_64
Comment 6 Ondřej Budai 2022-03-18 10:44:28 UTC 
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.
Comment 7 Jindrich Novy 2022-03-18 11:25:07 UTC 
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.
Comment 9 Xiaofeng Wang 2022-03-18 11:38:11 UTC 
Jindrich, I reported this bug on CS8. Thanks.
Comment 10 Xiaofeng Wang 2022-03-18 11:39:19 UTC 
My comment #5 "CentOS Stream 9" should be "CentOS Stream 8". Sorry.
Comment 11 Matthew Heon 2022-03-18 13:15:45 UTC 
This seems to be a build or packaging issue, Tom, I don't think I can offer any insight here
Comment 20 Joy Pu 2022-03-29 09:58:20 UTC 
Tested with podman-4.0.2-5 and the dependence already updated:
 
# rpm -qp --requires podman-4.0.2-5.module+el8.6.0+14594+d37c7ba8.x86_64.rpm | grep libsec
libseccomp >= 2.5
libseccomp.so.2()(64bit)
Comment 22 errata-xmlrpc 2022-05-10 13:28:28 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 (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
Note You need to log in before you can comment on or make changes to this bug.