Bake with Docker GitHub Builder | Docker Docs
Skip to content Search or ask Docker Search documentation Ask Docker Start a new chat Answers are generated based on the documentation. On this page: Docker Build The bake.yml reusable workflow builds from a Bake definition instead of a Dockerfile input set. This page shows how to call the workflow for a target, how to pass Bake overrides and variables, and how to export local output when a Bake file is already the source of truth for your build.
Build and push a Bake target The following workflow builds the image target from docker-bake.hcl and publishes the result with tags generated from metadata inputs : name : ci on : push : branches : - "main" tags : - "v*" pull_request : permissions : contents : read jobs : bake : uses : docker/github-builder/.github/workflows/bake.yml@v1 permissions : contents : read # to fetch the repository content id-token : write # for signing attestation(s) with GitHub OIDC Token with : output : image push : ${{ github.event_name != 'pull_request' }} target : image meta-images : name/app meta-tags : | type=ref,event=branch type=ref,event=pr type=semver,pattern={{version}} secrets : registry-auths : | - registry: docker.io username: ${{ vars.DOCKERHUB_USERNAME }} password: ${{ secrets.DOCKERHUB_TOKEN }} Bake workflows build one target per workflow call.
Groups and multi-target builds aren't supported because SLSA provenance , digest handling, and manifest creation are scoped to a single target. The workflow validates the definition before the build starts and resolves the target from the files you pass in files . Runner selection uses the same runner input as the Build workflow. Set a single GitHub-hosted Linux runner label or a platform mapping when the default mapping is not enough.
For details, see runner selection . Override target values and variables Because the workflow delegates the build to Bake, you can keep using set and vars for target-specific overrides: name : ci on : push : branches : - "main" permissions : contents : read jobs : bake : uses : docker/github-builder/.github/workflows/bake.yml@v1 permissions : contents : read # to fetch the repository content id-token : write # for signing attestation(s) with GitHub OIDC Token with : output : image push : true target : image vars : | IMAGE_TAG=${{ github.sha }} set : | *.args.BUILD_RUN_ID=${{ github.run_id }} *.platform=linux/amd64,linux/arm64 cache : true cache-scope : image meta-images : name/app meta-tags : | type=sha set-meta-annotations : true secrets : registry-auths : | - registry: docker.io username: ${{ vars.DOCKERHUB_USERNAME }} password: ${{ secrets.DOCKERHUB_TOKEN }} This form fits repositories that already use Bake groups, target inheritance, and variable expansion.
The reusable workflow takes care of Buildx setup, GitHub Actions cache export , Provenance defaults , signing behavior, and the final multi-platform manifest. Metadata labels and annotations can be merged into the Bake definition without adding a separate metadata step to your workflow. Export local output from Bake If the target should export files instead of publishing an image, switch the workflow output to local and upload the artifact: name : ci on : pull_request : permissions : contents : read jobs : bake : uses : docker/github-builder/.github/workflows/bake.yml@v1 permissions : contents : read # to fetch the repository content id-token : write # for signing attestation(s) with GitHub OIDC Token with : output : local target : binaries artifact-upload : true artifact-name : bake-output With output: local , the workflow injects the matching local output override into the Bake run and merges the uploaded artifacts after the per-platform builds finish.
For a Bake pattern that stays in a normal job, see Annotations with individual actions . If your build does not need a Bake definition, use build.yml instead.