CrazyMax

This would be part of build-push-action and bake-action. We have started to write docs about it https://github.com/docker/docs/pull/22215. It's not yet put upstream but you can test it: * https://github.com/crazy-max/.github?tab=readme-ov-file#build-distribute-mp *...

BuildKit 0.11.2 ```dockerfile FROM alpine AS base RUN apk add --no-cache tree RUN tree -apufi /tmp COPY foo.txt /tmp/foo.txt RUN tree -apufi /tmp COPY --link foo.txt /tmp/foo.txt RUN tree -apufi...

Someone reported a similar issue but without `--link`: https://github.com/docker/build-push-action/issues/1130#issuecomment-2163185050

Thanks for your feedback and sorry for the delay, feel free to open a PR. cc @margaale if you have time.

Seems like a bug, they should be merged over defaults.

I also see we don't merge over default for include/exclude tags for other providers: https://github.com/crazy-max/diun/blob/b3878678cbfc8866325b9b09da3efc8e887b1df5/internal/provider/common.go#L83-L86 We might revisit that as well.

Opened #179 to mitigate this issue. Can you try with: ```yaml uses: crazy-max/ghaction-virustotal@octokit-retry ``` Thanks

> This is for using contrib/cdisetup scripts with buildkit that is not built by our Dockerfile (buildkit-export-ubuntu target) ? Yes I was looking to move buildkit to debian base distro...

Maybe similar to issues we have since QEMU v7, can you try with v6.2.0: ```console $ docker run --rm --privileged tonistiigi/binfmt --uninstall qemu-* $ docker run --rm --privileged tonistiigi/binfmt:qemu-v6.2.0 --install...

``` failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N...