Bug 1928643

Summary:	Error: error streaming container content for copy up into volume
Product:	[Fedora] Fedora	Reporter:	Jan Pazdziora (Red Hat) <jpazdziora>
Component:	podman	Assignee:	Matthew Heon <mheon>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	acui, bbaude, container-sig, debarshir, dwalsh, jnovy, lsm5, mheon, pehunt, rh.container.bot, santiago
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1930134 (view as bug list)		Environment:
Last Closed:	2021-06-11 15:46:36 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:	1930134

Description Jan Pazdziora (Red Hat) 2021-02-15 09:28:45 UTC

Description of problem:

Container fails to start via podman if VOLUME is defined for directory that exists in the image.

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

podman-3.0.0-1.fc33.x86_64 from updates-testing

How reproducible:

Deterministic

Steps to Reproduce:
1. Have Dockerfile

FROM registry.fedoraproject.org/fedora:33
RUN dnf install -y systemd
VOLUME [ "/var/log/journal" ]
ENTRYPOINT [ "/usr/sbin/init" ]

2. Build image: podman build -t systemd .
3. Run container: podman run --rm -ti --name systemd systemd

Actual results:

Error: error streaming container content for copy up into volume 09fca6e31a8328bec38f12ae490b5dc6616a54876050e6d3adef4b1d7ee1a950: copier: get: globs [/log/journal] matched nothing (0 filtered out): no such file or directory

Expected results:

No error, systemd initialization output shown

Additional info:

It does not matter if I try this with rootless podman or via sudo.

This is a regression against podman 2.

Comment 1 Matthew Heon 2021-02-15 14:48:37 UTC

Similar, likely related upstream issue: https://github.com/containers/podman/issues/9354

Comment 2 Matthew Heon 2021-02-15 15:16:26 UTC

I can't reproduce. I've built the image and am running as specified, both with 3.0 and the latest code from the main branch, but I can't see the error you described. Can you provide any further details?

Comment 3 Matthew Heon 2021-02-15 15:17:21 UTC

Specifically would be interested in any environment details that may be unusual.

Comment 4 Matthew Heon 2021-02-15 15:45:01 UTC

Ah, nevermind. Confirmed this does reproduce on a fresh F33 VM.

Comment 5 Matthew Heon 2021-02-15 16:14:25 UTC

This is somehow environment related. My F33 development system does not exhibit the bug using any Podman I try, packaged or source-built; the fresh F33 VM always exhibits it on 3.0 and up, hand-built or packaged.

Comment 6 Matthew Heon 2021-02-15 16:45:59 UTC

I have a fix, but I am still extremely confused as to what's going on. The copying logic should not be environment-dependent, but it's acting extremely differently on two systems that should be similar.

Comment 7 Matthew Heon 2021-02-15 17:06:07 UTC

Fix PR: https://github.com/containers/podman/pull/9383

I'm still very suspicious of this one, however, given the lack of logic in how it reproduces. I'm going to look a bit more after lunch and try and figure out what's going on.

Comment 8 Jan Pazdziora (Red Hat) 2021-02-15 17:12:44 UTC

Mine is just a Fedora 33 upgraded from way back. But I also say it on Ubuntus in GitHub Actions https://github.com/adelton/freeipa-container/runs/1901775000?check_suite_focus=true and Travis CI https://travis-ci.com/github/adelton/freeipa-container/jobs/482976659

Comment 9 Daniel Walsh 2021-06-11 15:46:36 UTC

Looks like this is fixed in the current release