actions-marketplace-validations/Buildkit state

Load and save buildkit state.

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/isac322_builtkit-state@7140c0629f8dcac20aa6e81d8b87838a26a45c7d # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
buildx-name	Name of buildx. Fill as `name` output of `docker/setup-buildx-action` actions.	yes	—
cache-key	Unique id of cache. When loading, it is used for retrieval, and when saving, it is allocated to the cache.	yes	${{ runner.os }}-buildkit_state-${{ github.sha }}
cache-restore-keys	Keys to be used if the search with `cache-key` fails on load.	yes	${{ runner.os }}-buildkit_state-
target-types	Choose which type of BuildKit state to save. Since `exec.cachemount` corresponds to `mount=type=cache`, you can use the default value in most cases. Options: `regular`, `source.local`, `exec.cachemount`, `frontend`, `internal` (https://pkg.go.dev/github.com/moby/buildkit/client#UsageRecordType)	yes	exec.cachemount frontend
rewrite-cache	Whether to overwrite when the same cache key already exists.	—	false
save-on-failure	Whether to save cache even if job fails.	—	false
resume-builder	Resume buildx builder after successfully load cache and print disk usage.	—	true
compression-level	Zstd compression level (from 1 to 22)	—	3
window-size	Zstd window size (from 10 to 31)	—	27

name	description
restored-cache-key	Cache key restored from