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.

What AVCs were you seeing?

(In reply to Daniel Walsh from comment #1)
> What AVCs were you seeing?

Sorry Dan, I forgot to attach the AVC.

type=AVC msg=audit(1597418827.397:717): avc:  denied  { read } for  pid=92580 comm="echo" path="/usr/lib64/librt-2.28.so" dev="dm-0" ino=1465051 scontext=system_u:system_r:container_t:s0:c211,c704 tcontext=system_u:object_r:container_file_t:s0:c461,c1011 tclass=file permissive=0

This indicates that you have a container attempting to read content of a different container.

I am thinking you have mislabeled content under /var/lib/containers/

If you do podman system reset, do your containers start to work again?

I don't have the ENV now. I borrowed a beaker machine with latest container-tools module, container-selinux version is newer - 2:2.144.0-1.module+el8.3.0+7655+435bcef7, this issue does not exist. Then removed it and installed the reported version, this issue didn't show up either. It might be the ENV issue. I'll close this as NOT A BUG.