beenull/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Adds clarification to behavior of missing directories.

Browse source 
Closes #20920

Signed-off-by: Micah Zoltu <micah@zoltu.net>
This commit is contained in:
Micah Zoltu 2016-03-03 23:40:28 +00:00
parent 17156ba98f
commit 889d06178a
2 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/reference/commandline/cp.md
View file

@ -39,7 +39,8 @@ the user and primary group at the destination. For example, files copied to a
container are created with `UID:GID` of the root user. Files copied to the local container are created with `UID:GID` of the root user. Files copied to the local
machine are created with the `UID:GID` of the user which invoked the `docker cp` machine are created with the `UID:GID` of the user which invoked the `docker cp`
command. If you specify the `-L` option, `docker cp` follows any symbolic link command. If you specify the `-L` option, `docker cp` follows any symbolic link
in the `SRC_PATH`. in the `SRC_PATH`. `docker cp` does *not* create parent directories for
`DEST_PATH` if they do not exist.
Assuming a path separator of `/`, a first argument of `SRC_PATH` and second Assuming a path separator of `/`, a first argument of `SRC_PATH` and second
argument of `DEST_PATH`, the behavior is as follows: argument of `DEST_PATH`, the behavior is as follows:

3
man/docker-cp.1.md
View file

@ -36,7 +36,8 @@ the user and primary group at the destination. For example, files copied to a
container are created with `UID:GID` of the root user. Files copied to the local container are created with `UID:GID` of the root user. Files copied to the local
machine are created with the `UID:GID` of the user which invoked the `docker cp` machine are created with the `UID:GID` of the user which invoked the `docker cp`
command. If you specify the `-L` option, `docker cp` follows any symbolic link command. If you specify the `-L` option, `docker cp` follows any symbolic link
in the `SRC_PATH`. in the `SRC_PATH`. `docker cp` does *not* create parent directories for
`DEST_PATH` if they do not exist.
Assuming a path separator of `/`, a first argument of `SRC_PATH` and second Assuming a path separator of `/`, a first argument of `SRC_PATH` and second
argument of `DEST_PATH`, the behavior is as follows: argument of `DEST_PATH`, the behavior is as follows: