p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Change 'Uploading context' wording

Browse Source 
Docker-DCO-1.1-Signed-off-by: Ryan Stelly <ryan.stelly@live.com> (github: FLGMwt)
Upstream-commit: 47f850e550
Component: cli
This commit is contained in:
FLGMwt
2014-05-28 11:59:29 -05:00
committed by Tibor Vass
parent 2319cfb40b
commit c35401aba5
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
components/cli/docs/sources/reference/builder.md
View File

@ -23,7 +23,7 @@ Then call `docker build` with the path of you source repository as argument
The path to the source repository defines where to find the *context* of
the build. The build is run by the Docker daemon, not by the CLI, so the
whole context must be transferred to the daemon. The Docker CLI reports
"Uploading context" when the context is sent to the daemon.
"Sending build context to Docker daemon" when the context is sent to the daemon.
You can specify a repository and tag at which to save the new image if
the build succeeds:

2
components/cli/docs/sources/reference/commandline/cli.md
View File

@ -259,7 +259,7 @@ happens at the client side (where you're running
The transfer of context from the local machine to the Docker daemon is
what the `docker` client means when you see the
"Uploading context" message.
"Sending build context" message.
If you wish to keep the intermediate containers after the build is
complete, you must use `--rm=false`. This does not