Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3832 from crazy-max/20.10_backport_fix-docs-links 

[20.10 backport] docs: fix links to BuildKit backend
This commit is contained in:
Sebastiaan van Stijn 2022-10-25 13:53:02 -04:00 committed by GitHub
parent e814bd038d 3e3677e47d
commit baeda1f82a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 14 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/reference/commandline/build.md
View File

@ -323,13 +323,13 @@ directory from the context. Its effect can be seen in the changed size of the
uploaded context. The builder reference contains detailed information on uploaded context. The builder reference contains detailed information on
[creating a .dockerignore file](../builder.md#dockerignore-file). [creating a .dockerignore file](../builder.md#dockerignore-file).
When using the [BuildKit backend](../builder.md#buildkit), `docker build` searches When using the [BuildKit backend](https://docs.docker.com/build/buildkit/),
for a `.dockerignore` file relative to the Dockerfile name. For example, running `docker build` searches for a `.dockerignore` file relative to the Dockerfile
`docker build -f myapp.Dockerfile .` will first look for an ignore file named name. For example, running `docker build -f myapp.Dockerfile .` will first look
`myapp.Dockerfile.dockerignore`. If such a file is not found, the `.dockerignore` for an ignore file named `myapp.Dockerfile.dockerignore`. If such a file is not
file is used if present. Using a Dockerfile based `.dockerignore` is useful if a found, the `.dockerignore` file is used if present. Using a Dockerfile based
project contains multiple Dockerfiles that expect to ignore different sets of `.dockerignore` is useful if a project contains multiple Dockerfiles that
files. expect to ignore different sets of files.
### Tag an image (-t) ### Tag an image (-t)
@ -585,8 +585,9 @@ vndr
> **Note** > **Note**
> >
> This feature requires the BuildKit backend. You can either > This feature requires the BuildKit backend. You can either
> [enable BuildKit](../builder.md#buildkit) or use the [buildx](https://github.com/docker/buildx) > [enable BuildKit](https://docs.docker.com/build/buildkit/#getting-started) or
> plugin which provides more output type options. > use the [buildx](https://github.com/docker/buildx) plugin which provides more
> output type options.
### Specifying external cache sources ### Specifying external cache sources
@ -627,9 +628,9 @@ $ docker build --cache-from myname/myapp .
> **Note** > **Note**
> >
> This feature requires the BuildKit backend. You can either > This feature requires the BuildKit backend. You can either
> [enable BuildKit](../builder.md#buildkit) or use the [buildx](https://github.com/docker/buildx) > [enable BuildKit](https://docs.docker.com/build/buildkit/#getting-started) or
> plugin. The previous builder has limited support for reusing cache from > use the [buildx](https://github.com/docker/buildx) plugin. The previous
> pre-pulled images. > builder has limited support for reusing cache from pre-pulled images.
### Squash an image's layers (--squash) (experimental) ### Squash an image's layers (--squash) (experimental)

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

@ -78,7 +78,7 @@ line:
| `DOCKER_HOST` | Daemon socket to connect to. | | `DOCKER_HOST` | Daemon socket to connect to. |
| `DOCKER_STACK_ORCHESTRATOR` | Configure the default orchestrator to use when using `docker stack` management commands. | | `DOCKER_STACK_ORCHESTRATOR` | Configure the default orchestrator to use when using `docker stack` management commands. |
| `DOCKER_TLS_VERIFY` | When set Docker uses TLS and verifies the remote. This variable is used both by the `docker` CLI and the [`dockerd` daemon](dockerd.md) | | `DOCKER_TLS_VERIFY` | When set Docker uses TLS and verifies the remote. This variable is used both by the `docker` CLI and the [`dockerd` daemon](dockerd.md) |
| `BUILDKIT_PROGRESS` | Set type of progress output (`auto`, `plain`, `tty`) when [building](build.md) with [BuildKit backend](../builder.md#buildkit). Use plain to show container output (default `auto`). | | `BUILDKIT_PROGRESS` | Set type of progress output (`auto`, `plain`, `tty`) when [building](build.md) with [BuildKit backend](https://docs.docker.com/build/buildkit/). Use plain to show container output (default `auto`). |
Because Docker is developed using Go, you can also use any environment Because Docker is developed using Go, you can also use any environment
variables used by the Go runtime. In particular, you may find these useful: variables used by the Go runtime. In particular, you may find these useful: