CrazyMax

> I'm not sure why runDir is a const value, but if we can have an input on the variable, it may fix our issue. Yes I think we could...

> the XDG_RUNTIME_DIR, is being used while looking up docker.sock. If we have random char being attached by default, people using self-hosted need to create directory with exact random char...

I took a look at this one and it seems for `entitlements`, `annotations` and `attest` attributes we already append: https://github.com/docker/buildx/blob/921b576f3a26a93dbe5640fe34f421e5fb3fa83c/bake/bake.go#L963-L979. In such case `+=` is already the default for these...

Config looks good but are you sure content of `/etc/secret/key.json` is correct within the container (newlines, ...)? If it is then this might be an auth issue with upstream module...

I prefer to keep third-party integration outside of this repository but happy to put a link to your repo in the README

> ``` > remote* remote > \_ remote0 \_ tcp://buildkit.internal:3375 running 4cf5e34 linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/386 > ``` Seems like your machine does not support arm architectures which is why...

Oh my bad I can't read :see_no_evil: So yes platforms need to perfectly match otherwise it fails with this error because there is no proper linking between platforms in your...

> to check if `t.Platforms` is a subset of `t2.Platforms` instead of equality should suffice? Yeah maybe a subset would be enough but wonder if should not override with platforms...

> I'm able to run equivalent `docker buildx` steps to build and push images to Harbor using the same buildkit version (v0.21). Meaning you're able to push locally but not...

We have dedicated docs for GitHub Actions and secrets usage at https://docs.docker.com/build/ci/github-actions/secrets/ Manuals section also covers CLI usage: https://docs.docker.com/build/building/secrets/