docker/cli
1
0
Fork 0
mirror of https://github.com/docker/cli.git synced 2026-01-22 03:22:01 +03:00
Code Activity

Add some more specific help for Dockerfile build contexts.

Browse Source 
I've copy and pasted the error message so its googlable.

Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)
Upstream-commit: 6a55530c56
Component: cli
This commit is contained in:
SvenDowideit
2014-05-13 13:38:11 +10:00
committed by Tibor Vass
parent 9047b6bd9d
commit c17d1331c5
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -201,7 +201,8 @@ and a "context".
The files at `PATH` or `URL` are called the "context" of the build. The build
process may refer to any of the files in the context, for example when using an
[*ADD*](/reference/builder/#dockerfile-add) instruction. When a single Dockerfile is
given as `URL`, then no context is set.
given as `URL` or is piped through STDIN (`docker build - < Dockerfile`), then
no context is set.
When a Git repository is set as `URL`, then the
repository is used as the context. The Git repository is cloned with its
@@ -283,6 +284,13 @@ repository is used as Dockerfile. Note that you
can specify an arbitrary Git repository by using the `git://`
schema.
> **Note:** `docker build` will return a `no such file or directory` error
> if the file or directory does not exist in the uploaded context. This may
> happen if there is no context, or if you specify a file that is elsewhere
> on the Host system. The context is limited to the current directory (and its
> children) for security reasons, and to ensure repeatable builds on remote
> Docker hosts. This is also the reason why `ADD ../file` will not work.
## commit
Create a new image from a container᾿s changes