Browse code
Adds clarification to behavior of missing directories.
Closes #20920
Signed-off-by: Micah Zoltu <micah@zoltu.net>
Micah Zoltu authored on 2016/03/04 08:40:28Showing 2 changed files
| ... | ... |
@@ -39,7 +39,8 @@ the user and primary group at the destination. For example, files copied to a |
| 39 | 39 |
container are created with `UID:GID` of the root user. Files copied to the local |
| 40 | 40 |
machine are created with the `UID:GID` of the user which invoked the `docker cp` |
| 41 | 41 |
command. If you specify the `-L` option, `docker cp` follows any symbolic link |
| 42 |
-in the `SRC_PATH`. |
|
| 42 |
+in the `SRC_PATH`. `docker cp` does *not* create parent directories for |
|
| 43 |
+`DEST_PATH` if they do not exist. |
|
| 43 | 44 |
|
| 44 | 45 |
Assuming a path separator of `/`, a first argument of `SRC_PATH` and second |
| 45 | 46 |
argument of `DEST_PATH`, the behavior is as follows: |
| ... | ... |
@@ -36,7 +36,8 @@ the user and primary group at the destination. For example, files copied to a |
| 36 | 36 |
container are created with `UID:GID` of the root user. Files copied to the local |
| 37 | 37 |
machine are created with the `UID:GID` of the user which invoked the `docker cp` |
| 38 | 38 |
command. If you specify the `-L` option, `docker cp` follows any symbolic link |
| 39 |
-in the `SRC_PATH`. |
|
| 39 |
+in the `SRC_PATH`. `docker cp` does *not* create parent directories for |
|
| 40 |
+`DEST_PATH` if they do not exist. |
|
| 40 | 41 |
|
| 41 | 42 |
Assuming a path separator of `/`, a first argument of `SRC_PATH` and second |
| 42 | 43 |
argument of `DEST_PATH`, the behavior is as follows: |