Skip to content

docs(man): --file can sit outside the build context #7206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
locker95 wants to merge 1 commit into
base: master
Choose a base branch
from
+5 −6
Open

docs(man): --file can sit outside the build context #7206

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions man/docker-build.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,12 +54,11 @@ set as the **URL**, the repository is cloned locally and then sent as the contex

# OPTIONS
**-f**, **--file** *PATH/Dockerfile*
Path to the Dockerfile to use. If the path is a relative path and you are
building from a local directory, then the path must be relative to that
directory. If you are building from a remote URL pointing to either a
tarball or a Git repository, then the path must be relative to the root of
the remote context. In all cases, the file must be within the build context.
The default is *Dockerfile*.
Path to the Dockerfile to use. A relative path is resolved from the
current working directory, not from the build context. The file does
not have to live inside the context. When the context is a remote Git
repository or tarball, **-f** is relative to the root of that remote
context. The default is *Dockerfile*.

**--squash** *true*|*false*
**Experimental Only**
Expand Down