Bug 1461071

Summary: Docker: Handling uid/gid on docker cp
Product: Red Hat Enterprise Linux 7 Reporter: Jaroslav Spanko <jspanko>
Component: dockerAssignee: Antonio Murdaca <amurdaca>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: amurdaca, dornelas, dwalsh, jamills, jspanko, lsm5, lsu
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: docker-2:1.12.6-50.git0fdc778 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-05 10:35:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1186913, 1477427    

Description Jaroslav Spanko 2017-06-13 13:05:42 UTC
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

Comment 2 Daniel Walsh 2017-06-30 15:35:26 UTC
Antonio are these something we should back port?

Comment 3 Antonio Murdaca 2017-07-10 11:21:44 UTC
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

Comment 6 Luwen Su 2017-08-25 08:06:57 UTC
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.

Comment 8 errata-xmlrpc 2017-09-05 10:35:14 UTC
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