Added support for running with different builder

[ty2]

Introduced builder arguments to specify custom builder.

[AkihiroSuda]

Please rebase and rebuild the dist:

buildkit-cache-dance/.github/workflows/unit-tests.yml

Line 26 in 7c89267

run: pnpm i

Also please squash the commits

[ty2]

Please rebase and rebuild the dist:

buildkit-cache-dance/.github/workflows/unit-tests.yml

Line 26 in 7c89267

run: pnpm i

Also please squash the commits

Done.

[AkihiroSuda]

Commits do not seem squashed

https://www.freecodecamp.org/news/git-squash-commits/

[ty2]

Sorry, I'm not familiar with Git. It looks like the commits have been squashed. Could you check if there are any issues?

[AkihiroSuda]

Thanks

[kkopachev]

Hardcoding default builder name would break github actions setup with setup-buildx-action as it creates new builder with unique name and sets it as default, while the builder named default still exists, it is not selected for builds. When this action specifies --builder default it will use another builder, not the one for actual payload builds

[kkopachev]

I'd suggest using BUILDX_BUILDER environment variable instead of introducing new argument

[slinkydeveloper]

Stumbled on this in CI, used in combination with setup-buildx-action:

Run reproducible-containers/buildkit-cache-dance@v3

FROM ghcr.io/containerd/busybox:latest
COPY buildstamp buildstamp
RUN --mount=type=cache,target=/var/cache/sccache     --mount=type=bind,source=.,target=/var/dance-cache     cp -p -R /var/dance-cache/. /var/cache/sccache  || true

Error running command: docker buildx build --builder default -f scratch/Dancefile.inject --tag dance:inject sccache-cache
ERROR: use `docker --context=default buildx` to switch to context "default"

[slinkydeveloper]

Pinning the action version to 3.1.2 fixes it for me.