Exporters overview

KB at your finger tips

This is one stop global knowledge base where you can learn about all the products, solutions and support features.

Using exporters

To specify an exporter, use the following command syntax:

   $ docker buildx build --tag <registry>/<image> \
  --output type=<TYPE> .

Most common use cases doesnât require you donât need to specify which exporter to use explicitly. You only need to specify the exporter if you intend to customize the output somehow, or if you want to save it to disk. The --load and --push options allow Buildx to infer the exporter settings to use.

For example, if you use the --push option in combination with --tag , Buildx automatically uses the image exporter, and configures the exporter to push the results to the specified registry.

To get the full flexibility out of the various exporters BuildKit has to offer, you use the --output flag that lets you configure exporter options.

Use cases

Each exporter type is designed for different use cases. The following sections describe some common scenarios, and how you can use exporters to generate the output that you need.

Load to image store

Buildx is often used to build container images that can be loaded to an image store. Thatâs where the docker exporter comes in. The following example shows how to build an image using the docker exporter, and have that image loaded to the local image store, using the --output option:

   $ docker buildx build \
  --output type=docker,name=<registry>/<image> .

Buildx CLI will automatically use the docker exporter and load it to the image store if you supply the --tag and --load options:

   $ docker buildx build --tag <registry>/<image> --load .

  

Building images using the docker driver are automatically loaded to the local image store.

Images loaded to the image store are available to for docker run immediately after the build finishes, and youâll see them in the list of images when you run the docker images command.

Push to registry

To push a built image to a container registry, you can use the registry or image exporters.

When you pass the --push option to the Buildx CLI, you instruct BuildKit to push the built image to the specified registry:

   $ docker buildx build --tag <registry>/<image> --push .

  

Under the hood, this uses the image exporter, and sets the push parameter. Itâs the same as using the following long-form command using the --output option:

   $ docker buildx build \
  --output type=image,name=<registry>/<image>,push=true .

You can also use the registry exporter, which does the same thing:

   $ docker buildx build \
  --output type=registry,name=<registry>/<image> .

Export image layout to file

You can use either the oci or docker exporters to save the build results to image layout on your local filesystem. Both of these exporters generate a tar archive file containing the corresponding image layout. The dest parameter defines the target output path for the tarball.

   $ docker buildx build --output type=oci,dest=./image.tar .
[+] Building 0.8s (7/7) FINISHED
 ...
 => exporting to oci image format                                                                     0.0s
 => exporting layers                                                                                  0.0s
 => exporting manifest sha256:c1ef01a0a0ef94a7064d5cbce408075730410060e253ff8525d1e5f7e27bc900        0.0s
 => exporting config sha256:eadab326c1866dd247efb52cb715ba742bd0f05b6a205439f107cf91b3abc853          0.0s
 => sending tarball                                                                                   0.0s
$ mkdir -p out && tar -C out -xf ./image.tar
$ tree out
out
âââ blobs
âÂ Â  âââ sha256
âÂ Â      âââ 9b18e9b68314027565b90ff6189d65942c0f7986da80df008b8431276885218e
âÂ Â      âââ c78795f3c329dbbbfb14d0d32288dea25c3cd12f31bd0213be694332a70c7f13
âÂ Â      âââ d1cf38078fa218d15715e2afcf71588ee482352d697532cf316626164699a0e2
âÂ Â      âââ e84fa1df52d2abdfac52165755d5d1c7621d74eda8e12881f6b0d38a36e01775
âÂ Â      âââ fe9e23793a27fe30374308988283d40047628c73f91f577432a0d05ab0160de7
âââ index.json
âââ manifest.json
âââ oci-layout

  

Export filesystem

If you donât want to build an image from your build results, but instead export the filesystem that was built, you can use the local and tar exporters.

The local exporter unpacks the filesystem into a directory structure in the specified location. The tar exporter creates a tarball archive file.

   $ docker buildx build --output type=tar,dest=<path/to/output> .

  

The local exporter is useful in multi-stage builds since it allows you to export only a minimal number of build artifacts. For example, self-contained binaries.

Cache-only export

The cacheonly exporter can be used if you just want to run a build, without exporting any output. This can be useful if, for example, you want to run a test build. Or, if you want to run the build first, and create exports using subsequent commands. The cacheonly exporter creates a build cache, so any successive builds are instant.

   $ docker buildx build --output type=cacheonly

  

If you donât specify an exporter, and you donât provide short-hand options like --load that automatically selects the appropriate exporter, Buildx defaults to using the cacheonly exporter. Except if you build using the docker driver, in which case you use the docker exporter.

Buildx logs a warning message when using cacheonly as a default:

   $ docker buildx build .
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

  

Multiple exporters

You can only specify a single exporter for any given build (see this pull request for details){:target=âblankâ rel=ânoopenerâ class=â_â}. But you can perform multiple builds one after another to export the same content twice. BuildKit caches the build, so unless any of the layers change, all successive builds following the first are instant.

The following example shows how to run the same build twice, first using the image , followed by the local .

   $ docker buildx build --output type=image,tag=<registry>/<image> .
$ docker buildx build --output type=local,dest=<path/to/output> .

Configuration options

This section describes some configuration options available for exporters.

The options described here are common for at least two or more exporter types. Additionally, the different exporters types support specific parameters as well. See the detailed page about each exporter for more information about which configuration parameters apply.

The common parameters described here are:

Compression
OCI media type

Compression

When you export a compressed output, you can configure the exact compression algorithm and level to use. While the default values provide a good out-of-the-box experience, you may wish to tweak the parameters to optimize for storage vs compute costs. Changing the compression parameters can reduce storage space required, and improve image download times, but will increase build times.

To select the compression algorithm, you can use the compression option. For example, to build an image with compression=zstd :

   $ docker buildx build \
  --output type=image,name=<registry>/<image>,push=true,compression=zstd .

Use the compression-level=<value> option alongside the compression parameter to choose a compression level for the algorithms which support it:

0-9 for gzip and estargz
0-22 for zstd

As a general rule, the higher the number, the smaller the resulting file will be, and the longer the compression will take to run.

Use the force-compression=true option to force re-compressing layers imported from a previous image, if the requested compression algorithm is different from the previous compression algorithm.

Note

The gzip and estargz compression methods use the compress/gzip package, while zstd uses the github.com/klauspost/compress/zstd package.

OCI media types

Exporters that output container images, support creating images with either Docker media types (the default) or with OCI media types. This is supported by the image , registry , oci and docker exporters.

To export images with OCI media types set, use the oci-mediatypes property. For example, with the image exporter:

   $ docker buildx build \
  --output type=image,name=<registry>/<image>,push=true,oci-mediatypes=true .

Build info

Exporters that output container images, allow embedding information about the build, including information on the original build request and sources used during the build. This is supported by the image , registry , oci and docker exporters.

This build info is attached to the image configuration:

   {
  "moby.buildkit.buildinfo.v0": "<base64>"
}

  

By default, build dependencies are attached to the image configuration. You can turn off this behavior by setting buildinfo=false .

Whatâs next

Read about each of the exporters to learn about how they work and how to use them:

Image and registry exporters
OCI and Docker exporters.
Local and tar exporters

Local and tar exporters

The local and tar exporters output the root filesystem of the build result into a local directory. Theyâre useful for producing artifacts that arenât container images.

local exports files and directories.
tar exports the same, but bundles the export into a tarball.

Synopsis

Build a container image using the local exporter:

   $ docker buildx build --output type=local[,parameters] .

  

   $ docker buildx build --output type=tar[,parameters] .

  

The following table describes the available parameters:

Parameter	Type	Default	Description
`dest`	String	Â	Path to copy files to

Synopsis

Build a container image using the oci and docker exporters:

   $ docker buildx build --output type=oci[,parameters] .

  

   $ docker buildx build --output type=docker[,parameters] .

  

The following table describes the available parameters:

Parameter	Type	Default	Description
`name`	String	Â	Specify image name(s)
`dest`	String	Â	Path
`tar`	`true` , `false`	`true`	Bundle the output into a tarball layout
`compression`	`uncompressed` , `gzip` , `estargz` , `zstd`	`gzip`	Compression type, see compression
`compression-level`	`0..22`	Â	Compression level, see compression
`force-compression`	`true` , `false`	`false`	Forcefully apply compression, see compression
`oci-mediatypes`	`true` , `false`	Â	Use OCI media types in exporter manifests. Defaults to `true` for `type=oci` , and `false` for `type=docker` . See OCI Media types
`buildinfo`	`true` , `false`	`true`	Attach inline build info
`buildinfo-attrs`	`true` , `false`	`false`	Attach inline build info attributes
`annotation.<key>`	String	Â	Attach an annotation with the respective `key` and `value` to the built image,see annotations

Annotations

These exporters support adding OCI annotation using annotation.* dot notation parameter. The following example sets the org.opencontainers.image.title annotation for a build:

   $ docker buildx build \
    --output "type=<type>,name=<registry>/<image>,annotation.org.opencontainers.image.title=<title>" .

For more information about annotations, see BuildKit documentation.

Packaging your software

Build and package your application to run it anywhere: locally or in the cloud.

Multi-stage builds

Keep your images small and secure with minimal dependencies.

Multi-platform images

Build, push, pull, and run images seamlessly on different computer architectures.

Build drivers

Configure where and how you run your builds.

Build caching

Avoid unnecessary repetitions of costly operations, such as package installs.

Continuous integration

Learn how to use Docker in your continuous integration pipelines.

Exporters

Export any artifact you like, not just Docker images.

Bake

Orchestrate your builds with Bake.

Dockerfile frontend

Learn about the Dockerfile frontend for BuildKit.

Configure BuildKit

Take a deep dive into the internals of BuildKit to get the most out of your builds.

Read article

Install Docker Buildx

Docker Desktop

Docker Buildx is included by default in Docker Desktop.

Docker Engine via package manager

Docker Linux packages also include Docker Buildx when installed using the .deb or .rpm packages.

Install using a Dockerfile

Here is how to install and use Buildx inside a Dockerfile through the docker/buildx-bin image:

   # syntax=docker/dockerfile:1
FROM docker
COPY --from=docker/buildx-bin:latest /buildx /usr/libexec/docker/cli-plugins/docker-buildx
RUN docker buildx version

  

Download manually

Important

This section is for unattended installation of the Buildx component. These instructions are mostly suitable for testing purposes. We do not recommend installing Buildx using manual download in production environments as they will not be updated automatically with security updates.

On Windows, macOS, and Linux workstations we recommend that you install Docker Desktop instead. For Linux servers, we recommend that you follow the instructions specific for your distribution.

You can also download the latest binary from the releases page on GitHub.

Rename the relevant binary and copy it to the destination matching your OS:

OS	Binary name	Destination folder
Linux	`docker-buildx`	`$HOME/.docker/cli-plugins`
macOS	`docker-buildx`	`$HOME/.docker/cli-plugins`
Windows	`docker-buildx.exe`	`%USERPROFILE%\.docker\cli-plugins`

Or copy it into one of these folders for installing it system-wide.

On Unix environments:

/usr/local/lib/docker/cli-plugins OR /usr/local/libexec/docker/cli-plugins
/usr/lib/docker/cli-plugins OR /usr/libexec/docker/cli-plugins

On Windows:

C:\ProgramData\Docker\cli-plugins
C:\Program Files\Docker\cli-plugins

Note

On Unix environments, it may also be necessary to make it executable with chmod +x :
$ chmod +x ~/.docker/cli-plugins/docker-buildx

Set Buildx as the default builder

Running the command docker buildx install sets up the docker build command as an alias to docker buildx . This results in the ability to have docker build use the current Buildx builder.

To remove this alias, run docker buildx uninstall .

Read article

Build release notes

This page contains information about the new features, improvements, and bug fixes in Docker Buildx.

0.9.1

2022-08-18

Bug fixes and enhancements

The inspect command now displays the BuildKit version in use docker/buildx#1279
Fixed a regression when building Compose files that contain services without a build block docker/buildx#1277

For more details, see the complete release notes in the Buildx GitHub repository.

0.9.0

2022-08-17

New

Support for new driver remote that you can use to connect to any already running BuildKit instance docker/buildx#1078 docker/buildx#1093 docker/buildx#1094 docker/buildx#1103 docker/buildx#1134 docker/buildx#1204
You can now load Dockerfile from standard input even when the build context is coming from external Git or HTTP URL docker/buildx#994
Build commands now support new the build context type oci-layout:// for loading build context from local OCI layout directories. Note that this feature depends on an unreleased BuildKit feature and builder instance from moby/buildkit:master needs to be used until BuildKit v0.11 is released docker/buildx#1173
You can now use the new --print flag to run helper functions supported by the BuildKit frontend performing the build and print their results. You can use this feature in Dockerfile to show the build arguments and secrets that the current build supports with --print=outline and list all available Dockerfile stages with --print=targets . This feature is experimental for gathering early feedback and requires enabling BUILDX_EXPERIMENTAL=1 environment variable. We plan to update/extend this feature in the future without keeping backward compatibility docker/buildx#1100 docker/buildx#1272
You can now use the new --invoke flag to launch interactive containers from build results for an interactive debugging cycle. You can reload these containers with code changes or restore them to an initial state from the special monitor mode. This feature is experimental for gathering early feedback and requires enabling BUILDX_EXPERIMENTAL=1 environment variable. We plan to update/extend this feature in the future without enabling backward compatibility docker/buildx#1168 docker/buildx#1257 docker/buildx#1259
Buildx now understands environment variable BUILDKIT_COLORS and NO_COLOR to customize/disable the colors of interactive build progressbar docker/buildx#1230 docker/buildx#1226
buildx ls command now shows the current BuildKit version of each builder instance docker/buildx#998
The bake command now loads .env file automatically when building Compose files for compatibility docker/buildx#1261
Bake now supports Compose files with cache_to definition docker/buildx#1155
Bake now supports new builtin function timestamp() to access current time docker/buildx#1214
Bake now supports Compose build secrets definition docker/buildx#1069
Additional build context configuration is now supported in Compose files via x-bake docker/buildx#1256
Inspecting builder now shows current driver options configuration docker/buildx#1003 docker/buildx#1066

Updates

Updated the Compose Specification to 1.4.0 docker/buildx#1246 docker/buildx#1251

Bug fixes and enhancements

The buildx ls command output has been updated with better access to errors from different builders docker/buildx#1109
The buildx create command now performs additional validation of builder parameters to avoid creating a builder instance with invalid configuration docker/buildx#1206
The buildx imagetools create command can now create new multi-platform images even if the source subimages are located on different repositories or registries docker/buildx#1137
You can now set the default builder config that is used when creating builder instances without passing custom --config value docker/buildx#1111
Docker driver can now detect if dockerd instance supports initially disabled Buildkit features like multi-platform images docker/buildx#1260 docker/buildx#1262
Compose files using targets with . in the name are now converted to use _ so the selector keys can still be used in such targets docker/buildx#1011
Included an additional validation for checking valid driver configurations docker/buildx#1188 docker/buildx#1273
The remove command now displays the removed builder and forbids removing context builders docker/buildx#1128
Enable Azure authentication when using Kubernetes driver docker/buildx#974
Add tolerations handling for kubernetes driver docker/buildx#1045 docker/buildx#1053
Replace deprecated seccomp annotations with securityContext in kubernetes driver docker/buildx#1052
Fix panic on handling manifests with nil platform docker/buildx#1144
Fix using duration filter with prune command docker/buildx#1252
Fix merging multiple JSON files on Bake definition docker/buildx#1025
Fix issues with implicit builder created from Docker context had invalid configuration or dropped connection docker/buildx#1129
Fix conditions for showing no-output warning when using named contexts docker/buildx#968
Fix duplicating builders when builder instance and docker context have the same name docker/buildx#1131
Fix printing unnecessary SSH warning logs docker/buildx#1085
Fix possible panic when using an empty variable block with Bake JSON definition docker/buildx#1080
Fix image tools commands not handling --builder flag correctly docker/buildx#1067
Fix using custom image together with rootless option docker/buildx#1063

For more details, see the complete release notes in the Buildx GitHub repository.

0.8.2

2022-04-04

Updates

Update Compose spec used by buildx bake to v1.2.1 to fix parsing ports definition docker/buildx#1033

Bug fixes and enhancements

Fix possible crash on handling progress streams from BuildKit v0.10 docker/buildx#1042
Fix parsing groups in buildx bake when already loaded by a parent group docker/buildx#1021

For more details, see the complete release notes in the Buildx GitHub repository.

0.8.1

2022-03-21

Bug fixes and enhancements

Fix possible panic on handling build context scanning errors docker/buildx#1005
Allow . on Compose target names in buildx bake for backward compatibility docker/buildx#1018

For more details, see the complete release notes in the Buildx GitHub repository.

0.8.0

2022-03-09

New

Build command now accepts --build-context flag to define additional named build contexts for your builds docker/buildx#904
Bake definitions now support defining dependencies between targets and using the result of one target in another build docker/buildx#928 docker/buildx#965 docker/buildx#963 docker/buildx#962 docker/buildx#981
imagetools inspect now accepts --format flag allowing access to config and buildinfo for specific images docker/buildx#854 docker/buildx#972
New flag --no-cache-filter allows configuring build, so it ignores cache only for specified Dockerfile stages docker/buildx#860
Builds can now show a summary of warnings sets by the building frontend docker/buildx#892
The new build argument BUILDKIT_INLINE_BUILDINFO_ATTRS allows opting-in to embed building attributes to resulting image docker/buildx#908
The new flag --keep-buildkitd allows keeping BuildKit daemon running when removing a builder
- docker/buildx#852

Bug fixes and enhancements

--metadata-file output now supports embedded structure types docker/buildx#946
buildx rm now accepts new flag --all-inactive for removing all builders that are not currently running docker/buildx#885
Proxy config is now read from Docker configuration file and sent with build requests for backward compatibility docker/buildx#959
Support host networking in Compose docker/buildx#905 docker/buildx#880
Bake files can now be read from stdin with -f - docker/buildx#864
--iidfile now always writes the image config digest independently of the driver being used (use --metadata-file for digest) docker/buildx#980
Target names in Bake are now restricted to not use special characters docker/buildx#929
Image manifest digest can be read from metadata when pushed with docker driver docker/buildx#989
Fix environment file handling in Compose files docker/buildx#905
Show last access time in du command docker/buildx#867
Fix possible double output logs when multiple Bake targets run same build steps docker/buildx#977
Fix possible errors on multi-node builder building multiple targets with mixed platform docker/buildx#985
Fix some nested inheritance cases in Bake docker/buildx#914
Fix printing default group on Bake files docker/buildx#884
Fix UsernsMode when using rootless container docker/buildx#887

For more details, see the complete release notes in the Buildx GitHub repository.

0.7.1

2021-08-25

Fixes

Fix issue with matching exclude rules in .dockerignore docker/buildx#858
Fix bake --print JSON output for current group docker/buildx#857

For more details, see the complete release notes in the Buildx GitHub repository.

0.7.0

2021-11-10

New features

TLS certificates from BuildKit configuration are now transferred to build container with docker-container and kubernetes drivers docker/buildx#787
Builds support --ulimit flag for feature parity docker/buildx#800
Builds support --shm-size flag for feature parity docker/buildx#790
Builds support --quiet for feature parity docker/buildx#740
Builds support --cgroup-parent flag for feature parity docker/buildx#814
Bake supports builtin variable BAKE_LOCAL_PLATFORM docker/buildx#748
Bake supports x-bake extension field in Compose files docker/buildx#721
kubernetes driver now supports colon-separated KUBECONFIG docker/buildx#761
kubernetes driver now supports setting Buildkit config file with --config docker/buildx#682
kubernetes driver now supports installing QEMU emulators with driver-opt docker/buildx#682

Enhancements

Allow using custom registry configuration for multi-node pushes from the client docker/buildx#825
Allow using custom registry configuration for buildx imagetools command docker/buildx#825
Allow booting builder after creating with buildx create --bootstrap docker/buildx#692
Allow registry:insecure output option for multi-node pushes docker/buildx#825
BuildKit config and TLS files are now kept in Buildx state directory and reused if BuildKit instance needs to be recreated docker/buildx#824
Ensure different projects use separate destination directories for incremental context transfer for better performance docker/buildx#817
Build containers are now placed on separate cgroup by default docker/buildx#782
Bake now prints the default group with --print docker/buildx#720
docker driver now dials build session over HTTP for better performance docker/buildx#804

Fixes

Fix using --iidfile together with a multi-node push docker/buildx#826
Using --push in Bake does not clear other image export options in the file docker/buildx#773
Fix Git URL detection for buildx bake when https protocol was used docker/buildx#822
Fix pushing image with multiple names on multi-node builds docker/buildx#815
Avoid showing --builder flags for commands that donât use it docker/buildx#818
Unsupported build flags now show a warning docker/buildx#810
Fix reporting error details in some OpenTelemetry traces docker/buildx#812

For more details, see the complete release notes in the Buildx GitHub repository.

0.6.3

2021-08-30

Fixes

Fix BuildKit state volume location for Windows clients docker/buildx#751

For more details, see the complete release notes in the Buildx GitHub repository.

0.6.2

2021-08-21

For more details, see the complete release notes in the Buildx GitHub repository.

Fixes

Fix connection error showing up in some SSH configurations docker/buildx#741

0.6.1

2021-07-30

Enhancements

Set ConfigFile to parse compose files with Bake docker/buildx#704

Fixes

Duplicate progress env var docker/buildx#693
Should ignore nil client docker/buildx#686

For more details, see the complete release notes in the Buildx GitHub repository.

0.6.0

2021-07-16

New features

Support for OpenTelemetry traces and forwarding Buildx client traces to BuildKit docker/buildx#635
Experimental GitHub Actions remote cache backend with --cache-to type=gha and --cache-from type=gha docker/buildx#535
New --metadata-file flag has been added to build and Bake command that allows saving build result metadata in JSON format docker/buildx#605
This is the first release supporting Windows ARM64 docker/buildx#654
This is the first release supporting Linux Risc-V docker/buildx#652
Bake now supports building from remote definition with local files or another remote source as context docker/buildx#671
Bake now allows variables to reference each other and using user functions in variables and vice-versa docker/buildx#575 docker/buildx#539 docker/buildx#532
Bake allows defining attributes in the global scope docker/buildx#541
Bake allows variables across multiple files docker/buildx#538
New quiet mode has been added to progress printer docker/buildx#558
kubernetes driver now supports defining resources/limits docker/buildx#618
Buildx binaries can now be accessed through buildx-bin Docker image docker/buildx#656

Enhancements

docker-container driver now keeps BuildKit state in volume. Enabling updates with keeping state docker/buildx#672
Compose parser is now based on new compose-go parser fixing support for some newer syntax docker/buildx#669
SSH socket is now automatically forwarded when building an ssh-based git URL docker/buildx#581
Bake HCL parser has been rewritten docker/buildx#645
Extend HCL support with more functions docker/buildx#491 docker/buildx#503
Allow secrets from environment variables docker/buildx#488
Builds with an unsupported multi-platform and load configuration now fail fast docker/buildx#582
Store Kubernetes config file to make buildx builder switchable docker/buildx#497
Kubernetes now lists all pods as nodes on inspection docker/buildx#477
Default Rootless image has been set to moby/buildkit:buildx-stable-1-rootless docker/buildx#480

Fixes

imagetools create command now correctly merges JSON descriptor with old one docker/buildx#592
Fix building with --network=none not requiring extra security entitlements docker/buildx#531

For more details, see the complete release notes in the Buildx GitHub repository.

0.5.1

2020-12-15

Fixes

Fix regression on setting --platform on buildx create outside kubernetes driver docker/buildx#475

For more details, see the complete release notes in the Buildx GitHub repository.

0.5.0

2020-12-15

New features

The docker driver now supports the --push flag docker/buildx#442
Bake supports inline Dockerfiles docker/buildx#398
Bake supports building from remote URLs and Git repositories docker/buildx#398
BUILDX_CONFIG env var allow users to have separate buildx state from Docker config docker/buildx#385
BUILDKIT_MULTI_PLATFORM build arg allows to force building multi-platform return objects even if only one --platform specified docker/buildx#467

Enhancements

Allow --append to be used with kubernetes driver docker/buildx#370
Build errors show error location in source files and system stacktraces with --debug docker/buildx#389
Bake formats HCL errors with source definition docker/buildx#391
Bake allows empty string values in arrays that will be discarded docker/buildx#428
You can now use the Kubernetes cluster config with the kubernetes driver docker/buildx#368 docker/buildx#460
Creates a temporary token for pulling images instead of sharing credentials when possible docker/buildx#469
Ensure credentials are passed when pulling BuildKit container image docker/buildx#441 docker/buildx#433
Disable user namespace remapping in docker-container driver docker/buildx#462
Allow --builder flag to switch to default instance docker/buildx#425
Avoid warn on empty BUILDX_NO_DEFAULT_LOAD config value docker/buildx#390
Replace error generated by quiet option by a warning docker/buildx#403
CI has been switched to GitHub Actions docker/buildx#451 docker/buildx#463 docker/buildx#466 docker/buildx#468 docker/buildx#471

Fixes

Handle lowercase Dockerfile name as a fallback for backward compatibility docker/buildx#444

For more details, see the complete release notes in the Buildx GitHub repository.

0.4.2

2020-08-22

New features

Support cacheonly exporter docker/buildx#337

Enhancements

Update go-cty to pull in more stdlib functions docker/buildx#277
Improve error checking on load docker/buildx#281

Fixes

Fix parsing json config with HCL docker/buildx#280
Ensure --builder is wired from root options docker/buildx#321
Remove warning for multi-platform iidfile docker/buildx#351

For more details, see the complete release notes in the Buildx GitHub repository.

0.4.1

2020-05-01

Fixes

Fix regression on flag parsing docker/buildx#268
Fix using pull and no-cache keys in HCL targets docker/buildx#268

For more details, see the complete release notes in the Buildx GitHub repository.

0.4.0

2020-04-30

New features

Add kubernetes driver docker/buildx#167
New global --builder flag to override builder instance for a single command docker/buildx#246
New prune and du commands for managing local builder cache docker/buildx#249
You can now set the new pull and no-cache options for HCL targets docker/buildx#165

Enhancements

Upgrade Bake to HCL2 with support for variables and functions docker/buildx#192
Bake now supports --load and --push docker/buildx#164
Bake now supports wildcard overrides for multiple targets docker/buildx#164
Container driver allows setting environment variables via driver-opt docker/buildx#170

For more details, see the complete release notes in the Buildx GitHub repository.

0.3.1

2019-09-27

Enhancements

Handle copying unix sockets instead of erroring docker/buildx#155 moby/buildkit#1144

Fixes

Running Bake with multiple Compose files now merges targets correctly docker/buildx#134
Fix bug when building a Dockerfile from stdin ( build -f - ) docker/buildx#153

For more details, see the complete release notes in the Buildx GitHub repository.

0.3.0

2019-08-02

New features

Custom buildkitd daemon flags docker/buildx#102
Driver-specific options on create docker/buildx#122

Enhancements

Environment variables are used in Compose files docker/buildx#117
Bake now honors --no-cache and --pull docker/buildx#118
Custom BuildKit config file docker/buildx#121
Entitlements support with build --allow docker/buildx#104

Fixes

Fix bug where --build-arg foo would not read foo from environment docker/buildx#116

For more details, see the complete release notes in the Buildx GitHub repository.

0.2.2

2019-05-30

Enhancements

Change Compose file handling to require valid service specifications docker/buildx#87

For more details, see the complete release notes in the Buildx GitHub repository.

0.2.1

2019-05-25

New features

Add BUILDKIT_PROGRESS env var docker/buildx#69
Add local platform docker/buildx#70

Enhancements

Keep arm variant if one is defined in the config docker/buildx#68
Make dockerfile relative to context docker/buildx#83

Fixes

Fix parsing target from compose files docker/buildx#53

For more details, see the complete release notes in the Buildx GitHub repository.

0.2.0

2019-04-25

New features

First release

For more details, see the complete release notes in the Buildx GitHub repository.

Read article

Welcome to Knowledge Base!

KB at your finger tips

Exporters overview

Using exporters

Use cases

Load to image store

Push to registry

Export image layout to file

Export filesystem

Cache-only export

Multiple exporters

Configuration options

Compression

OCI media types

Build info

Whatâs next

Local and tar exporters

Synopsis

Further reading

OCI and Docker exporters

Synopsis

Annotations

Further reading

Overview of Docker Build

Packaging your software

Multi-stage builds

Multi-platform images

Build drivers

Build caching

Continuous integration

Exporters

Bake

Dockerfile frontend

Configure BuildKit

Install Docker Buildx

Docker Desktop

Docker Engine via package manager

Install using a Dockerfile

Download manually

Set Buildx as the default builder

Build release notes

0.9.1

Bug fixes and enhancements

0.9.0

New

Updates

Bug fixes and enhancements

0.8.2

Updates

Bug fixes and enhancements

0.8.1

Bug fixes and enhancements

0.8.0

New

Bug fixes and enhancements

0.7.1

Fixes

0.7.0

New features

Enhancements

Fixes

0.6.3

Fixes

0.6.2

Fixes

0.6.1

Enhancements

Fixes

0.6.0

New features

Enhancements

Fixes

0.5.1

Fixes

0.5.0

New features

Enhancements

Fixes

0.4.2

New features

Whatâs next