b81a28fa8b
Fixes #1992 Right now when you `docker cp` a path which is in a volume, the cp itself works, however you end up getting files that are in the container's fs rather than the files in the volume (which is not in the container's fs). This makes it so when you `docker cp` a path that is in a volume it follows the volume to the real path on the host. archive.go has been modified so that when you do `docker cp mydata:/foo .`, and /foo is the volume, the outputed folder is called "foo" instead of the volume ID (because we are telling it to tar up `/var/lib/docker/vfs/dir/<some id>` and not "foo", but the user would be expecting "foo", not the ID Signed-off-by: Brian Goff <cpuguy83@gmail.com> |
||
|---|---|---|
| .. | ||
| testdata | ||
| archive.go | ||
| archive_test.go | ||
| changes.go | ||
| changes_test.go | ||
| diff.go | ||
| MAINTAINERS | ||
| README.md | ||
| time_linux.go | ||
| time_unsupported.go | ||
| wrap.go | ||
This code provides helper functions for dealing with archive files.