moved context arg to last

Signed-off-by: David Karlsson <david.karlsson@docker.com>
pull/1334/head
David Karlsson 2 years ago
parent f51884e893
commit f5a1d8bff9

@ -41,7 +41,7 @@ When you run a build, Buildx pulls the specified `image` (by default,
started, Buildx submits the build submitted to the containerized build server. started, Buildx submits the build submitted to the containerized build server.
```console ```console
$ docker buildx build . -t <image> --builder=container $ docker buildx build -t <image> --builder=container .
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
#1 [internal] booting buildkit #1 [internal] booting buildkit
#1 pulling image moby/buildkit:buildx-stable-1 #1 pulling image moby/buildkit:buildx-stable-1
@ -59,7 +59,7 @@ Unlike when using the default `docker` driver, images built with the
Use the `--load` flag: Use the `--load` flag:
```console ```console
$ docker buildx build . --load -t <image> --builder=container $ docker buildx build --load -t <image> --builder=container .
... ...
=> exporting to oci image format 7.7s => exporting to oci image format 7.7s
=> => exporting layers 4.9s => => exporting layers 4.9s
@ -86,11 +86,11 @@ architectures that you want to build for.
For example, to build a Linux image for `amd64` and `arm64`: For example, to build a Linux image for `amd64` and `arm64`:
```console ```console
$ docker buildx build . \ $ docker buildx build \
--builder=container \ --builder=container \
--platform=linux/amd64,linux/arm64 \ --platform=linux/amd64,linux/arm64 \
-t <registry>/<image> \ -t <registry>/<image> \
--push --push .
``` ```
> **Warning** > **Warning**

@ -135,11 +135,11 @@ output to.
For example, to build a Linux image for `amd64` and `arm64`: For example, to build a Linux image for `amd64` and `arm64`:
```console ```console
$ docker buildx build . \ $ docker buildx build \
--builder=kube \ --builder=kube \
--platform=linux/amd64,linux/arm64 \ --platform=linux/amd64,linux/arm64 \
-t <user>/<image> \ -t <user>/<image> \
--push --push .
``` ```
> **Warning** > **Warning**
@ -309,10 +309,10 @@ Prerequisites:
```console ```console
# Replace <registry> with your Docker username # Replace <registry> with your Docker username
# and <image> with the name of the image you want to build # and <image> with the name of the image you want to build
docker buildx build . \ docker buildx build \
--builder=kube \ --builder=kube \
-t <registry>/<image> \ -t <registry>/<image> \
--push --push .
``` ```
That's it! You've now built an image from a Kubernetes pod, using Buildx! That's it! You've now built an image from a Kubernetes pod, using Buildx!

@ -75,7 +75,7 @@ You can switch to this new builder as the default using
`docker buildx use remote-unix`, or specify it per build using `--builder`: `docker buildx use remote-unix`, or specify it per build using `--builder`:
```console ```console
$ docker buildx build . --builder=remote-unix -t test --load $ docker buildx build --builder=remote-unix -t test --load .
``` ```
Remember that you need to use the `--load` flag if you want to load the build Remember that you need to use the `--load` flag if you want to load the build

Loading…
Cancel
Save