Bug 1674519

Summary:	Not able to create volumes using Dockerfile using podman
Product:	Red Hat Enterprise Linux 8	Reporter:	Suhaas Bhat <subhat>
Component:	podman	Assignee:	Brent Baude <bbaude>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	ddarrah, dornelas, dwalsh, igreen, jligon, lsm5, mheon, ypu
Target Milestone:	rc
Target Release:	8.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	podman 1.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 21:01:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1186913, 1734574

Description Suhaas Bhat 2019-02-11 14:28:50 UTC

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

Comment 1 Daniel Walsh 2019-03-01 10:09:05 UTC

Fixed in podman 1.1

Comment 3 Joy Pu 2019-09-27 12:38:16 UTC

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'
#

Comment 4 Joy Pu 2019-09-28 12:05:56 UTC

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

Comment 6 errata-xmlrpc 2019-11-05 21:01:33 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, 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