Wrong permissions on idmapped volumes created before starting the container when container-dir does not exist #22228
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Issue Description
Same as #21608:
Unfortunately, the fix (#21611) does not work if the container-dir does not exist in the container.
Steps to reproduce the issue
Steps to reproduce the issue
podman volume create test
(asroot
)podman run --rm --userns=auto -v test:/test:idmap archlinux touch /test/123
(asroot
)Describe the results you received
The process is unable to create the file, due to wrong permissions.
Describe the results you expected
The process being able to create the file.
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
N/A
Additional information
I noticed this while trying to use the "new"
:idmap
option (as described in #16250) withgitlab-runner
, which creates the volumes first and then uses them (and apparently the container-dir does not exist in the container).The text was updated successfully, but these errors were encountered: