Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Handle of uid/gid for docker cp and API

How reproducible:
Fully reproducable 

Actual results:
docker cp does not handle uid/gid of files

Expected results:
Handle uid/gid for docker cp and API

Additional info:
Upstream issue and pull which will be available in 17.06 most probably
https://github.com/moby/moby/issues/21651
https://github.com/moby/moby/pull/28923

Antonio are these something we should back port?

Yes, we need to back port this one. Could you please provide the docker version of your docker so I know where to back port this? Thanks

Backported though:

-
 https://github.com/projectatomic/docker/commit/e852150e85fbdff01fb6c9977343f5261966009b
-
 https://github.com/projectatomic/docker/commit/4fb8bb1d09b83f3b6cc9b603dfd498c6cbd02233
-
 https://github.com/projectatomic/docker/commit/c66c3ebda70ca4710bf362f68cd6a59039d28f70

In docker-1.12.6-55.gitc4618fb.el7.x86_64,

In VM,
# ll
total 4
-rw-rw-r--. 1 test test   0 Aug 25 15:44 test
-rw-rw-r--. 1 test test 106 Aug 25 15:44 test.tar.gz

Container inside:
-rw-rw-r--.   1 1000 1000  106 Aug 25 07:44 test.tar.gz

move to verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2599