Hide Forgot
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.
Similar, likely related upstream issue: https://github.com/containers/podman/issues/9354
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?
Specifically would be interested in any environment details that may be unusual.
Ah, nevermind. Confirmed this does reproduce on a fresh F33 VM.
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.
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.
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.
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
Looks like this is fixed in the current release