docker bake

Use the args attribute to define build arguments for the target. This has the same effect as passing a --build-arg flag to the build command. You can set args attributes to use null values. Doing so forces the target to use the ARG value specified in the Dockerfile.

The annotations attribute lets you add annotations to images built with bake. The key takes a list of annotations, in the format of KEY=VALUE.

The attest attribute lets you apply build attestations to the target. This attribute accepts the long-form CSV version of attestation parameters.

Build cache sources. The builder imports cache from the locations you specify. It uses the Buildx cache storage backends, and it works the same way as the --cache-from flag. This takes a list value, so you can specify multiple cache sources.

Build cache export destinations. The builder exports its build cache to the locations you specify. It uses the Buildx cache storage backends, and it works the same way as the --cache-to flag. This takes a list value, so you can specify multiple cache export targets.

Specifies the location of the build context to use for this target. Accepts a URL or a directory path. This is the same as the build context positional argument that you pass to the build command.

Additional build contexts. This is the same as the --build-context flag. This attribute takes a map, where keys result in named contexts that you can reference in your builds. You can specify different types of contexts, such local directories, Git URLs, and even other Bake targets. Bake automatically determines the type of a context based on the pattern of the context value.

Uses the string value as an inline Dockerfile for the build target. The dockerfile-inline takes precedence over the dockerfile attribute. If you specify both, Bake uses the inline version.

Name of the Dockerfile to use for the build. This is the same as the --file flag for the docker build command.

A target can inherit attributes from other targets. Use inherits to reference from one target to another.

Assigns image labels to the build. This is the same as the --label flag for docker build. t's possible to use a null value for labels. If you do, the builder uses the label value specified in the Dockerfile.

A matrix strategy lets you fork a single target into multiple different variants, based on parameters that you specify. This works in a similar way to [Matrix strategies for GitHub Actions]. You can use this to reduce duplication in your bake definition. The matrix attribute is a map of parameter names to lists of values. Bake builds each possible combination of values as a separate target. Each generated target must have a unique name. To specify how target names should resolve, use the name attribute.

Specify name resolution for targets that use a matrix strategy.

Don't use build cache for the specified stages. This is the same as the --no-cache-filter flag for docker build.

Don't use cache when building the image. This is the same as the --no-cache flag for docker build.

Configuration for exporting the build output. This is the same as the --output flag.

Set target platforms for the build target. This is the same as the --platform flag.

Configures whether the builder should attempt to pull images when building the target. This is the same as the --pull flag for docker build.

Defines secrets to expose to the build target. This is the same as the --secret flag.

Defines SSH agent sockets or keys to expose to the build. This is the same as the --ssh flag. This can be useful if you need to access private repositories during a build.

Image names and tags to use for the build target. This is the same as the --tag flag.

Set the target build stage to build. This is the same as the --target flag.

Ulimits overrides the default ulimits of build's containers when using RUN instructions and are specified with a soft and hard limit as such: =[:].