[Bug]: podman uidmapping and gidmapping with an idmapped volume #17433
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
Under Debian SID, the
podman uidmapping and gidmapping with an idmapped volume
test (test/e2e/run_userns_test.go:118) test fails under root, rootless, and remote scenarios. Note: The all CI Debian VM's are setup to use runc and CgroupsV1 (not the default).Steps to reproduce the issue
Steps to reproduce the issue
podman --storage-opt vfs.imagestore=/tmp/imagecachedir --root /tmp/podman_test331015218/root --runroot /tmp/podman_test331015218/runroot --runtime runc --conmon /usr/bin/conmon --network-config-dir /etc/containers/networks --network-backend netavark --cgroup-manager systemd --tmpdir /tmp/podman_test331015218 --events-backend file --storage-driver vfs run --uidmap=0:1:500 --gidmap=0:200:5000 -v my-foo-volume:/foo:Z,idmap alpine stat -c #%u:%g# /foo
Describe the results you received
#65534:65534#
Describe the results you expected
#0:0#
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
This is occurring within an initial integration of Debian SID VMs in podman's CI setup. It's easily and reliably reproducible.
Additional information
The text was updated successfully, but these errors were encountered: