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

build: use buildx build for hb 

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson 2023-08-22 17:52:54 +02:00
parent 15d60f191c
commit 46541f0530
1 changed files with 22 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
content/build/hydrobuild.md
View File

@ -21,12 +21,12 @@ cache, ensuring fast builds anywhere and for all team members.
## How Hydrobuild works ## How Hydrobuild works
Using Hydrobuild is no different from running a regular build. You invoke a Using Hydrobuild is no different from running a regular build. You invoke a
build the same way you normally would, using `docker build`. The difference is build the same way you normally would, using `docker buildx build`. The
in where and how that build gets executed. difference is in where and how that build gets executed.
By default when you invoke a `docker build` command, your build runs on a local By default when you invoke a build command, the build runs on a local instance
instance of BuildKit, bundled with the Docker daemon. With Hydrobuild, you send of BuildKit, bundled with the Docker daemon. With Hydrobuild, you send the
the build request to a BuildKit instance running remotely, in the cloud. build request to a BuildKit instance running remotely, in the cloud.
The remote builder executes the build steps, and sends the resulting build The remote builder executes the build steps, and sends the resulting build
output to the destination that you specify. For example, back to your local output to the destination that you specify. For example, back to your local
@ -138,7 +138,7 @@ To run a build using Hydrobuild, invoke a build command and specify the
name of the builder using the `--builder` flag. name of the builder using the `--builder` flag.
```console ```console
$ docker build --builder hydrobuild --tag myorg/some-tag . $ docker buildx build --builder hydrobuild --tag myorg/some-tag .
``` ```
> **Note** > **Note**
@ -154,7 +154,7 @@ If you created a [multi-platform builder](#create-a-multi-platform-builder),
you can build multi-platform images using the `--platform` flag: you can build multi-platform images using the `--platform` flag:
```console ```console
$ docker build --builder hydrobuild \ $ docker buildx build --builder hydrobuild \
--platform linux/amd64,linux/arm64 \ --platform linux/amd64,linux/arm64 \
--tag myorg/some-tag --push . --tag myorg/some-tag --push .
``` ```
@ -170,7 +170,7 @@ $ docker build --builder hydrobuild \
> image store. > image store.
> >
> When building multi-platform images, consider pushing the resulting image to > When building multi-platform images, consider pushing the resulting image to
> a registry directly, using the `docker build --push` flag. > a registry directly, using the `docker buildx build --push` flag.
### Use by default ### Use by default
@ -181,6 +181,19 @@ make it the selected builder:
$ docker buildx use hydrobuild --global $ docker buildx use hydrobuild --global
``` ```
> **Note**
>
> Changing your default builder with `docker buildx use` only changes the
> default builder for the `docker buildx build` command. The shorthand `docker
> build` command will still use the `default` builder unless you specify the
> `--builder` flag explicitly.
>
> If you use build scripts, such as `make`, we recommend that you update your
> build commands from `docker build` to `docker buildx build`, to avoid any
> confusion with regards to builder selection. Alternatively, you can run
> `docker buildx install` to make the default `docker build` command behave
> like `docker buildx build`, without discrepancies.
### GitHub Actions ### GitHub Actions
You can use GitHub Actions in combination with Hydrobuild to achieve faster You can use GitHub Actions in combination with Hydrobuild to achieve faster
@ -378,4 +391,4 @@ No. Your interface to Hydrobuild is Buildx, and you can use the existing
For more information, refer to: For more information, refer to:
- [docker buildx build --secret](../engine/reference/commandline/buildx_build.md#secret) - [docker buildx build --secret](../engine/reference/commandline/buildx_build.md#secret)
- [docker buildx build --ssh](../engine/reference/commandline/buildx_build.md#ssh) - [docker buildx build --ssh](../engine/reference/commandline/buildx_build.md#ssh)