This action implements the same inputs and outputs as the docker/bake-action, but uses the depot CLI to execute the build.

• Depot bake-action GitHub Action
  • Table of Contents
  • Setup
  • Usage
    • Authentication
    • Differences from docker/bake-action
  • Inputs
    • Depot-specific inputs
    • General inputs
  • Outputs
  • License

The depot CLI will need to be available in your workflow, you can use the depot/setup-action to install it:

steps:
  - uses: depot/setup-action@v1

This action implements the same inputs and outputs as the docker/bake-action. You will need to supply your project ID and Depot authentication information, although both can be inferred from the environment. See below for more details.

This action needs a Depot API token to communicate with your project's builders. You can supply this one of three ways. The third, using OIDC, is the preferred method, but you can also supply a token directly.

1. You can supply a user or project API token via the token input:

   steps:
     - uses: depot/bake-action@v1
       with:
         token: ${{ secrets.DEPOT_TOKEN }}

2. You can supply a user or project API token via the DEPOT_TOKEN environment variable:

   steps:
     - uses: depot/bake-action@v1
       env:
         DEPOT_TOKEN: ${{ secrets.DEPOT_TOKEN }}

3. Depot supports GitHub's OpenID Connect tokens via a trust relationship, so your Actions builds can securely authenticate with your Depot projects without any static access tokens. To configure the trust relationship, visit your Depot project settings, then add your repository and desired workflow config to Trust Relationships. Then in your workflow, enable the id-token: write permission:

   permissions:
     # allow issuing OIDC tokens for this workflow run
     id-token: write
     # allow at least reading the repo contents, add other permissions if necessary
     contents: read
   steps:
     # no need to provide a DEPOT_TOKEN
     - uses: depot/bake-action@v1

1. Authentication — this action needs to authenticate with a Depot API token to communicate with your project's builders (see above).

2. If you have not configured a depot.json file with depot init, you can explicitly specify your project ID via the project input:

   steps:
     - uses: depot/build-push-action@v1
       with:
         project: abc123xyz

3. The builder input is not supported - this action always runs builds using Depot's hosted builders, if you need to route builds to a local buildx builder, you should use the docker/build-push-action.

The following inputs can be used as step.with keys and match the inputs from docker/bake-action:

MIT License, see LICENSE.

Code derived from docker/bake-action copyright 2013-2018 Docker, Inc., Apache License, Version 2.0.