{"id":1699,"date":"2025-02-05T22:18:41","date_gmt":"2025-02-05T22:18:41","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2025\/02\/05\/docker-bake-is-now-generally-available-in-docker-desktop-4-38\/"},"modified":"2025-02-05T22:18:41","modified_gmt":"2025-02-05T22:18:41","slug":"docker-bake-is-now-generally-available-in-docker-desktop-4-38","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2025\/02\/05\/docker-bake-is-now-generally-available-in-docker-desktop-4-38\/","title":{"rendered":"Docker Bake is Now Generally Available in Docker Desktop 4.38!"},"content":{"rendered":"

We\u2019re excited to announce the General Availability of Docker Bake<\/strong> with Docker Desktop 4.38<\/a>! This powerful build orchestration tool takes the hassle out of managing complex builds and offers simplicity, flexibility, and performance for teams of all sizes.<\/p>\n

What is Docker Bake?<\/h2>\n

Docker Bake is an orchestration tool that streamlines Docker builds, similar to how Compose simplifies managing runtime environments. With Bake, you can define build stages and deployment environments in a declarative file, making complex builds easier to manage. It also leverages BuildKit\u2019s parallelization and optimization features to speed up build times.<\/p>\n

While Dockerfiles are excellent for defining image build steps, teams often need to build multiple images and execute helper tasks like testing, linting, and code generation. Traditionally, this meant juggling numerous docker build commands with their own options and arguments \u2013 a tedious and error-prone process.<\/p>\n

Bake changes the game by introducing a declarative file format that encapsulates all options and image dependencies, referred to as targets<\/strong><\/a>. Additionally, Bake\u2019s ability to parallelize and deduplicate work ensures faster and more efficient builds.<\/p>\n

Why should you use Bake?<\/h2>\n

Challenges with complex Docker Build configuration:<\/h3>\n

Managing long, complex build commands filled with countless flags and environment variables.<\/p>\n

Tedious workflows for building multiple images.<\/p>\n

Difficulty declaring builds for specific targets or environments.<\/p>\n

Requires a script or 3rd-party tool to make things manageable<\/p>\n

Docker Bake tackles these challenges with a better way to manage complex builds with a simple, declarative approach.<\/p>\n

Key benefits of Docker Bake<\/h3>\n

Simplicity<\/strong>: Replace complex chains of Docker build commands and scripts with a single docker buildx bake command while maintaining clear, version-controlled configuration files that are easy to understand and modify.<\/p>\n

Flexibility<\/strong>: Express sophisticated build logic through HCL syntax and matrix builds, enabling dynamic configurations that adapt to different environments and requirements while supporting custom functions for advanced use cases.<\/p>\n

Consistency<\/strong>: Maintain standardized build configurations across teams and environments through version-controlled files and inheritance patterns, eliminating environment-specific build issues and reducing configuration drift.<\/p>\n

Performance<\/strong>: Automatically parallelize independent builds and eliminate redundant operations through context deduplication and intelligent caching, dramatically reducing build times for complex multi-image workflows.<\/p>\n

Figure 1<\/strong>: One simple Docker buildx bake command to replace all the flags and environment variables.<\/p>\n

Use cases for Docker Bake<\/h3>\n

1. Monorepo and Image Bakery<\/h4>\n

Docker Bake can help developers efficiently manage and build multiple related Docker images from a single source repository. Plus, they can leverage shared configurations and automated dependency handling to enforce organizational standards.<\/p>\n

Development Efficiency:<\/strong> Teams can maintain consistent build logic across dozens or hundreds of microservices in a single repository, reducing configuration drift and maintenance overhead.<\/p>\n

Resource Optimization:<\/strong> Shared base images and contexts are automatically deduplicated, dramatically reducing build times and storage costs.<\/p>\n

Standardization:<\/strong> Enforce organizational standards through inherited configurations, ensuring all services follow security, tagging, and testing requirements.<\/p>\n

Change Management:<\/strong> A single source of truth for build configurations makes it easier to implement organization-wide changes like base image updates or security patches.<\/p>\n

2. Compose users<\/h4>\n

Docker Bake provides seamless compatibility with existing docker-compose.yml files, allowing direct use of your current configurations. Existing Compose users are able to get started using Bake with minimal effort.<\/p>\n

Gradual Adoption:<\/strong> Teams can incrementally adopt advanced build features while still leveraging their existing compose workflows and knowledge.<\/p>\n

Development Consistency:<\/strong> Use the same configuration for both local development (via compose) and production builds (via Bake), eliminating \u201cworks on my machine\u201d issues.<\/p>\n

Enhanced Capabilities<\/strong>: Access powerful features like matrix builds and HCL expressions while maintaining compatibility with familiar compose syntax.<\/p>\n

CI\/CD Integration<\/strong>: Seamlessly integrate with existing CI\/CD pipelines that already understand compose files while adding Bake\u2019s advanced build capabilities.<\/p>\n

3. Complex build configurations<\/h4>\n

Developers can use targets<\/a>, groups<\/a>, variables<\/a>, functions<\/a>, and matrix targets<\/a> and many more tools in Bake to simplify their build configurations across projects and teams.<\/p>\n

Cross-Platform Compatibility:<\/strong> Matrix builds enable teams to efficiently manage builds across multiple architectures, OS versions, and dependency combinations from a single configuration.<\/p>\n

Dynamic Adaptation:<\/strong> HCL expressions allow builds to adapt to different environments, git branches, or CI variables without maintaining multiple configurations.<\/p>\n

Build Optimization:<\/strong> Custom functions enable sophisticated logic for things like version calculation, tag generation, and conditional builds based on git history.<\/p>\n

Quality Control:<\/strong> Variable validation and inheritance ensure consistent configuration across complex build scenarios, reducing errors and maintenance burden.<\/p>\n

Scale Management:<\/strong> Groups and targets help organize large-scale build systems with dozens or hundreds of permutations, making them manageable and maintainable.<\/p>\n

4. Docker Build Cloud<\/h4>\n

With Bake-optimized builds as the foundation, developers can achieve more efficient Docker Build Cloud performance and faster builds.<\/p>\n

Enhanced Docker Build Cloud Performance:<\/strong> Instantly parallelize matrix builds across cloud infrastructure, turning hour-long build pipelines into minutes without managing build infrastructure.<\/p>\n

Resource Optimization:<\/strong> Leverage Build Cloud\u2019s distributed caching and deduplication to dramatically reduce bandwidth usage and build times, which is especially valuable for remote teams.<\/p>\n

Cost Management:<\/strong> Save cost with DBC \u2014<\/strong> Bake\u2019s precise target definitions mean you only consume cloud resources for exactly what needs to be built.<\/p>\n

Developer Experience:<\/strong> Teams can run complex multi-architecture builds without powerful local machines, enabling development from any device while maintaining build performance.<\/p>\n

CI\/CD Enhancement:<\/strong> Offload resource-intensive builds from CI runners to Build Cloud, reducing CI costs and queue times while improving reliability.<\/p>\n

What\u2019s New in Bake for GA?<\/h2>\n

Docker Bake has been an experimental feature for several years, allowing us to refine and improve it based on user feedback. So, there is already a strong set of ingredients that users love, such as targets<\/a> and groups<\/a>, variables<\/a>, HCL Expression Support<\/a>, inheritance<\/a> capabilities, matrix targets<\/a>, and additional contex<\/a>ts. With this GA release, Bake is now ready for production use, and we\u2019ve added several enhancements to make it more efficient, secure, and easier to use:<\/p>\n

Deduplicated Context Transfers<\/strong><\/a>:<\/strong> Significantly speeds up build pipelines by eliminating redundant file transfers when multiple targets share the same build context.<\/p>\n

Entitlements<\/strong><\/a>:<\/strong> Enhances security and resource management by providing fine-grained control over what capabilities and resources builders can access during the build process.<\/p>\n

Composable Attributes<\/strong><\/a>:<\/strong> Simplifies configuration management by allowing teams to define reusable attribute sets that can be mixed, matched, and overridden across different targets.<\/p>\n

Variable Validation<\/strong><\/a>:<\/strong> Prevents wasted time and resources by catching configuration errors before the actual build process begins.<\/p>\n

Deduplicate context transfers<\/h3>\n

When you build targets concurrently using groups, build contexts are loaded independently for each target. If the same context is used by multiple targets in a group, that context is transferred once for each time it\u2019s used. This can significantly impact build time, depending on your build configuration.<\/p>\n

Previously, the workaround required users to define a named context that loads the context files and then have each target reference the named context. But with Bake, this will be handled automatically now.<\/p>\n

Bake can automatically deduplicate context transfers from targets sharing the same context. When you build targets concurrently using groups, build contexts are loaded independently for each target. If the same context is used by multiple targets in a group, that context is transferred once for each time it\u2019s used. This more efficient approach leads to much faster build time.\u00a0<\/p>\n

Read more about how to speed up your build time in our docs<\/a>.\u00a0<\/p>\n

Entitlements<\/h3>\n

Bake now includes entitlements to control access to privileged operations, aligning with Build. This prevents unintended side effects and security risks. If Bake detects a potential issue \u2014 like a privileged access request or an attempt to access files outside the current directory \u2014 the build will fail unless explicitly allowed.<\/p>\n

To be consistent, the Bake command now supports the –allow=ENTITLEMENT flag to grant access to additional entitlements. The following entitlements are currently supported for Bake<\/a>.<\/p>\n

Build equivalents<\/p>\n

–allow network.host \u2014<\/strong> Allows executions with host networking.<\/p>\n

–allow security.insecure \u2014<\/strong> Allows executions without sandbox. (i.e. \u2014privileged)<\/p>\n

File system: Grant filesystem access for builds that need access files outside the working directory. This will impact context, output, cache-from, cache-to, dockerfile, secret<\/p>\n

–allow fs=<path|*> \u2014<\/strong> Grant read and write access to files outside the working directory.<\/p>\n

–allow fs.read=<path|*> \u2014<\/strong> Grant read access to files outside the working directory.<\/p>\n

–allow fs.write=<path|*> \u2014<\/strong> Grant write access to files outside the working directory.<\/p>\n

ssh<\/p>\n

–allow ssh \u2014<\/strong>\u2013 Allows exposing SSH agent.<\/p>\n

Composable attributes<\/h3>\n

Several attributes previously had to be defined in CSV (e.g. type=provenance,mode=min). These were challenging to read and couldn\u2019t be easily overridden. The following can now be defined as structured objects:<\/p>\n

target “app” {
\n\t\tattest = [
\n\t\t\t{ type = “provenance”, mode = “max” },
\n\t\t\t{ type = “sbom”, disabled = true}
\n\t\t]<\/p>\n

\t\tcache-from = [
\n\t\t\t{ type = “registry”, ref = “user\/app:cache” },
\n\t\t\t{ type = “local”, src = “path\/to\/cache”}
\n\t\t]<\/p>\n

\t\tcache-to = [
\n\t\t\t{ type = “local”, dest = “path\/to\/cache” },
\n\t\t]<\/p>\n

\t\toutput = [
\n\t\t\t{ type = “oci”, dest = “..\/out.tar” },
\n\t\t\t{ type = “local”, dest=”..\/out”}
\n\t\t]<\/p>\n

\t\tsecret = [
\n\t\t\t{ id = “mysecret”, src = “path\/to\/secret” },
\n\t\t\t{ id = “mysecret2”, env = “TOKEN” },
\n\t\t]<\/p>\n

\t\tssh = [
\n\t\t\t{ id = “default” },
\n\t\t\t{ id = “key”, paths = [“path\/to\/key”] },
\n\t\t]
\n}<\/p>\n

As such, the attributes are now composable. Teams can mix, match, and override attributes across different targets which simplifies configuration management.<\/p>\n

target “app-dev” {
\n attest = [
\n\t\t\t{ type = “provenance”, mode = “min” },
\n\t\t\t{ type = “sbom”, disabled = true}
\n\t\t]
\n }<\/p>\n

target “app-prod” {
\n inherits = [“app-dev”]<\/p>\n

attest = [
\n\t\t\t{ type = “provenance”, mode = “max” },
\n\t\t]
\n }<\/p>\n

Variable validation<\/h3>\n

Bake now supports validation for variables similar to Terraform<\/a> to help developers catch and resolve configuration errors early. The GA for Bake also supports the following use cases.<\/p>\n

Basic validation<\/strong><\/p>\n

To verify that the value of a variable conforms to an expected type, value range, or other condition, you can define custom validation rules using the validation block.<\/p>\n

variable “FOO” {
\n validation {
\n condition = FOO != “”
\n error_message = “FOO is required.”
\n }
\n}<\/p>\n

target “default” {
\n args = {
\n FOO = FOO
\n }
\n}<\/p>\n

Multiple validations<\/strong><\/p>\n

To evaluate more than one condition, define multiple validation blocks for the variable. All conditions must be true.<\/p>\n

variable “FOO” {
\n validation {
\n condition = FOO != “”
\n error_message = “FOO is required.”
\n }
\n validation {
\n condition = strlen(FOO) > 4
\n error_message = “FOO must be longer than 4 characters.”
\n }
\n}<\/p>\n

target “default” {
\n args = {
\n FOO = FOO
\n }
\n}<\/p>\n

Dependency on other variables<\/strong><\/p>\n

You can reference other Bake variables<\/a> in your condition expression, enabling validations that enforce dependencies between variables. This ensures that dependent variables are set correctly before proceeding.<\/p>\n

variable “FOO” {}
\nvariable “BAR” {
\n validation {
\n condition = FOO != “”
\n error_message = “BAR requires FOO to be set.”
\n }
\n}<\/p>\n

target “default” {
\n args = {
\n BAR = BAR
\n }
\n}<\/p>\n

New Bake options<\/h3>\n

In addition to updating the Bake configuration, we\u2019ve added a new \u2013list option. Previously, if you were unfamiliar with a project or wanted a reminder of the supported targets and variables, you would have to read through the file. Now, the list option will allow you to quickly query a list of them. It also supports the JSON format option if you need programmatic access.<\/p>\n

List target<\/strong><\/p>\n

Quickly get a list of the targets available in your Bake configuration.<\/p>\n

docker buildx bake –list targets<\/p>\n

docker buildx bake –list type=targets,format=json<\/p>\n

List variables<\/strong><\/p>\n

Get a list of variables available for your Bake configuration.<\/p>\n

docker buildx bake –list variables<\/p>\n

docker buildx bake –list type=variables,format=json<\/p>\n

These improvements build on a powerful feature set, ensuring Bake is both reliable and future-ready.<\/p>\n

Get started with Docker Bake<\/h2>\n

Ready to simplify your builds? Update to Docker Desktop 4.38 today and start using Bake. With its declarative syntax and advanced features, Docker Bake is here to help you build faster, more efficiently, and with less effort.<\/p>\n

Explore the documentation<\/a> to learn how to create your first Bake file and experience the benefits of streamlined builds firsthand.<\/p>\n

Let\u2019s bake something amazing together!<\/p>","protected":false},"excerpt":{"rendered":"

We\u2019re excited to announce the General Availability of Docker Bake with Docker Desktop 4.38! This powerful build orchestration tool takes […]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[4],"tags":[],"class_list":["post-1699","post","type-post","status-publish","format-standard","hentry","category-docker"],"_links":{"self":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/1699","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/comments?post=1699"}],"version-history":[{"count":0,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/1699\/revisions"}],"wp:attachment":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/media?parent=1699"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/categories?post=1699"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/tags?post=1699"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}