Bug 1218599 - docker can no longer copy from inside the container
Summary: docker can no longer copy from inside the container
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: docker-io
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-05 11:27 UTC by Nikos Mavrogiannopoulos
Modified: 2015-08-21 03:25 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-21 03:25:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dockerfile reproducer (98 bytes, text/plain)
2015-05-05 11:27 UTC, Nikos Mavrogiannopoulos
no flags Details

Description Nikos Mavrogiannopoulos 2015-05-05 11:27:08 UTC
Created attachment 1022155 [details]
dockerfile reproducer

Description of problem:
After upgrading docker I can no longer cp from inside a container. I upgraded to docker-io-1.6.0-4.git350a636.fc21.x86_64 and tried docker-io-1.6.0-4.git350a636.fc21.x86_64 as well. Both fail.

This is a regression in F21. That worked fine with 1.3.2

How reproducible:
Outside the container use:
docker cp my_container:/tmp/file-created-in-the-container ./tmp/
FATA[0000] Error response from daemon: Could not find the file ...

Using ssh I can verify that the files exist

Steps to Reproduce:
0. Copy the attached dockerfile into docker-dir
1. sudo docker build -t test-image docker-dir
2. sudo docker run -P --privileged=true --name xxx-name test-image
3. sudo docker cp xxx-name:/tmp/xxx /tmp/

Actual results:
With 1.3.2: nothing. The file is copied.

With 1.6.0:
FATA[0000] Error response from daemon: Could not find the file /tmp/xxx in container xxx-name 

Expected results:
The file should have been copied.

Comment 1 Nikos Mavrogiannopoulos 2015-05-05 11:30:22 UTC
This is quite important to me as I base my test suite on F21 and docker, and updating docker completely breaks my test suite.

Comment 2 Daniel Walsh 2015-06-03 12:11:54 UTC
Should be fixed in docker-1.6.2.

We had made a change to mount the /tmp directory by default as a tmpfs, which we are changing back to the default, which should allow this behavior to work again.

We are working on a new command atomic mount which will expose the entire image to the host, and would allow you do do much more with host commands like cp, rsync ...


Note You need to log in before you can comment on or make changes to this bug.