Skip to content

Copy to container is not consistent with docker for images with no explicit user #27538

@matejvasek

Description

@matejvasek

Issue Description

When using docker cp into a container based on a image with no explicit user the uid/gids form the tar stream are always used irrespective of the the --archive CLI flag (the copyUIDGID query param).

This kinda makes sense, if the user is not set (even if root is implied is such a situation) you cannot chown to the primary User of container since it is not there.

Podman behaves differently if there is no explicit user it fully assumes the root user. So when using podman cp or calling the compat API the copied files may end up being owned by root depending or the --archive flag or the copyUIDGID query param.

Steps to reproduce the issue

Steps to reproduce the issue
1.
2.
3.

Describe the results you received

Describe the results you received

Describe the results you expected

Describe the results you expected

podman info output

If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.

Podman in a container

No

Privileged Or Rootless

None

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

Metadata

Metadata

Assignees

Labels

bugweekkind/bugCategorizes issue or PR as related to a bug.triagedIssue has been triagedvolunteers-wantedIssues good for community/volunteer contributions

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions