CrazyMax

> ``` > docker/setup-buildx-action#20 exporting to image > docker/setup-buildx-action#20 exporting manifest sha256:35e18d8d4307852968643876c6b989f9b84fddacba4ca295188f25c7a26ffca5 done > docker/setup-buildx-action#20 exporting config sha256:794f12649df6de63a6738f3869bdabb14fd52fe2764e5d2aff3588628e6a0e33 done > docker/setup-buildx-action#20 exporting attestation manifest sha256:c6dca146f2990a48b1f8aae54b5748eeae0b6813f5edab5cf9b5ae8f8e81d1d1 done > docker/setup-buildx-action#20 exporting manifest...

Looking at the logs it tries to push `ghcr.io/tenant:0.0.0` which doesn't sounds right as it's missing the repo name. Hence why you got a 400. Do you have a link...

See https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners to distribute build across multiple runners. To use this example with bake you can look at https://github.com/crazy-max/docker-osxcross/pull/24 Best is ofc to use a builder with native nodes against...

fixed in https://github.com/moby/buildkit/pull/3178

> that said, I'm not really sure about the auto-snapshot thingy too... seems easy enough to check on the workflow if the current commit is a tag or not, and...

@caarlos0 Major bump was the right move, thanks!

Diun only checks digest for specified image name (tag included) from database with the one being fetched but there is no relation between tags like a registry would do atm....

This is also slightly related to #114

Atm BuildKit integration tests don't run with the containerd snapshotter. With https://github.com/moby/buildkit/pull/3176 we could but we need https://github.com/moby/moby/pull/44686 first and make changes to the buildkit workflow. Wonder if we should...

Reminder that the buildkit workflow doesn't run tests for containerd integration with this PR atm. You could cherry pick https://github.com/moby/moby/pull/44908 to make sure everything works.