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:
We are not able to create volumes using Dockerfile

Version-Release number of selected component (if applicable):
podman-1.0.0-1.git82e8011.module+el8+2696+e59f0461.x86_64

dockerfile :
----------------------
FROM rhel7
VOLUME abc
----------------------

STEP 1: FROM rhel7
STEP 2: VOLUME /hello
--> 061bc907371bfcf186541551509d83855bba14e4a491694c54288b3b4ec958ab
STEP 3: COMMIT test
--> cac5bdbd8cfe53545f6bdd45843cca8dd68e01283ba7c436997fe3a2b2aaeca6

It shows the entry of volume in userdata/volumes/  for that container

Issue is only with #podman volume ls command

Expectation:

podman volume ls should list the name of created volumes

Fixed in podman 1.1

Test with container-selinux-2.107-2.module+el8.1.0+4081+b29780af.noarch, the rules are already dropped. So set this to verified.

Details:
# sesearch --allow | grep 'svirt_sandbox_domain unconfined_service_t'
#

Test with steps in https://github.com/containers/libpod/issues/2170. Can reproduce with podman-0.12.1.2-3.git9551f6b.module+el8+2591+d9a63299.x86_64, test with podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64, after run a container with the image, the volume can be created as expect. So set this to verified.
Details:
After build
# podman run -d test
b0a7e173b70a1237a862310fae9b22073cde0b6a5bc738e0689a2132d69912e2

# podman volume ls
DRIVER   VOLUME NAME
local    cf33b1ad4e5c5aba2d63c90c0f5b3f057408c41692b95e0d818c065b13874e97

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, 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-2019:3403