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:

Please see https://github.com/containers/podman/issues/11031


Version-Release number of selected component (if applicable):

Podman 3.2.x plus recent containers-common.

How reproducible:

Always


Steps to Reproduce:
1. $ podman --runtime=runc run fedora echo it works

Actual results:

Error: unable to start container process: error adding seccomp filter rule for syscall bdflush: permission denied: OCI permission denied

(or similar)


Expected results:

it works

Additional info:

Proposed fix: https://github.com/containers/podman/pull/11039

Can we get qa ack here please?

Kir, does this need to go to podman-3.3 too or not?

Not needed in podman 3.3 as of https://github.com/containers/podman/pull/10690/commits/b6662eed3f27ac5466501b046db4f1608845af61

This bug has been verified on podman-3.3.0-2.module+el8.5.0+12136+c1ac9593.


[root@kvm-07-guest24 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.5 Beta (Ootpa)

[root@kvm-07-guest24 ~]# rpm -q runc podman kernel
runc-1.0.1-4.module+el8.5.0+12048+8939a3ea.x86_64
podman-3.3.0-2.module+el8.5.0+12136+c1ac9593.x86_64
kernel-4.18.0-325.el8.x86_64

[root@kvm-07-guest24 ~]# rpm -qf /usr/share/containers/seccomp.json
containers-common-1.4.0-4.module+el8.5.0+12136+c1ac9593.x86_64

[root@kvm-07-guest24 ~]# podman --runtime=runc run -it --rm quay.io/libpod/alpine:latest echo hello
hello

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-2021:4154