You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### <a name="file"></a> Specify a Dockerfile (-f, --file)
594
594
595
595
```console
596
596
$ docker build -f Dockerfile.debug .
@@ -637,17 +637,17 @@ examples: |-
637
637
> repeatable builds on remote Docker hosts. This is also the reason why
638
638
> `ADD ../file` does not work.
639
639
640
-
### Use a custom parent cgroup (--cgroup-parent)
640
+
### <a name="cgroup-parent"></a> Use a custom parent cgroup (--cgroup-parent)
641
641
642
642
When `docker build` is run with the `--cgroup-parent` option the containers
643
643
used in the build will be run with the [corresponding `docker run` flag](../run.md#specify-custom-cgroups).
644
644
645
-
### Set ulimits in container (--ulimit)
645
+
### <a name="ulimit"></a> Set ulimits in container (--ulimit)
646
646
647
647
Using the `--ulimit` option with `docker build` will cause each build step's
648
-
container to be started using those [`--ulimit` flag values](run.md#set-ulimits-in-container---ulimit).
648
+
container to be started using those [`--ulimit` flag values](run.md#ulimit).
649
649
650
-
### Set build-time variables (--build-arg)
650
+
### <a name="build-arg"></a> Set build-time variables (--build-arg)
651
651
652
652
You can use `ENV` instructions in a Dockerfile to define variable
653
653
values. These values persist in the built image. However, often
@@ -682,16 +682,16 @@ examples: |-
682
682
$ docker build --build-arg HTTP_PROXY .
683
683
```
684
684
685
-
This is similar to how `docker run -e` works. Refer to the [`docker run` documentation](https://docs.docker.com/engine/reference/commandline/run/#set-environment-variables--e---env---env-file)
685
+
This is similar to how `docker run -e` works. Refer to the [`docker run` documentation](run.md#env)
0 commit comments