Replies: 1 comment
-
This is the expected behavior, podman uses the extra configured uids/gids from /etc/sub{u,g}id. As most container images contain more than one uid we have to write different uids to the storage. If you want to chown/delete files you must use |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Issue Description
I am running podman as a regular user (rootless) explicitly setting the root directory to a particular location. When podman creates the images the 'partial' folders always seem to be having a random user id as owner but the user's group id:
$ ls -l containers/root/overlay/8b845b0d3b07a3aa40e875124add71a06ff27637e29805aee92841df571e6c8d/diff/var/cache/apt/archives/ total 4 -rw-r-----. 1 rstreif rstreif 0 May 23 11:01 lock drwx------. 2 100041 rstreif 4096 May 23 11:01 partial
Due to the ownership and permission settings the user cannot read/write the partial directory. The only workaround is to change ownership as root. However, that is not practical in an automated build environment.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
'partial' directory is owned by a non-existing user with the user id 100041. All other directories are correctly owned by the user running podman.
Describe the results you expected
The 'partial' directory should also be owned by the user running podman.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
Beta Was this translation helpful? Give feedback.
All reactions