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.
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 (container-tools:2.0 bug fix 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/RHBA-2021:0269
Verified on podman-1.6.4-17.module+el8.2.0+9347+d4fa9cbb.x86_64 w/ runc-1.0.0-64.rc10.module+el8.2.0+9347+d4fa9cbb.x86_64. # sh -x run.sh + IMAGE=quay.io/libpod/alpine + podman run --name myctr1 -td quay.io/libpod/alpine Trying to pull quay.io/libpod/alpine... Getting image source signatures Copying blob 9d16cba9fb96 done Copying config 9617696764 done Writing manifest to image destination Storing signatures f52306261fbe06236ba966baba3c0df26a0a2f89627270207c0b4c4f4ef80e64 + podman run --name myctr2 -td quay.io/libpod/alpine 3ee90be4e0d0ad7951d0686a2269b3cf83391e78d3a300e4f6562a0c992de39b + timeout 5 podman exec myctr1 sleep 10 + podman kill myctr1 f52306261fbe06236ba966baba3c0df26a0a2f89627270207c0b4c4f4ef80e64 + grep Exec -A3 + podman inspect myctr1 "ExecIDs": [ "82cb031f7804bc8e70a73a9b2ccbb24dcf5fec5d3fc24fa8262d89027b2466fd" ], "GraphDriver": { + podman rm myctr1 f52306261fbe06236ba966baba3c0df26a0a2f89627270207c0b4c4f4ef80e64 + timeout 5 podman exec myctr2 sleep 10 + podman stop myctr2 3ee90be4e0d0ad7951d0686a2269b3cf83391e78d3a300e4f6562a0c992de39b + grep Exec -A3 + podman inspect myctr2 "ExecIDs": [], "GraphDriver": { "Name": "overlay", "Data": { + podman rm myctr2 3ee90be4e0d0ad7951d0686a2269b3cf83391e78d3a300e4f6562a0c992de39b