I found out that using this action triggers https://github.com/docker/buildx/issues/177, but what's surprising is that it seems to happen solely because of the iidfile argument
Here is the base of my action (the setup if you want):
The later calls /usr/bin/docker buildx build --tag silex/nix:latest --platform linux/amd64,linux/arm64 --iidfile /tmp/docker-build-push-thK9oA/iidfile --cache-from silex/nix:latest --cache-to type=inline --pull --push . and to me it's the same command as the one that is working except the iidfile argument.
Hello,
I found out that using this action triggers https://github.com/docker/buildx/issues/177, but what's surprising is that it seems to happen solely because of the
iidfile
argumentHere is the base of my action (the setup if you want):
So at this point all is fine, the builders are ready to build & push the image.
What I found out is that this works:
While this doesn't:
The later calls
/usr/bin/docker buildx build --tag silex/nix:latest --platform linux/amd64,linux/arm64 --iidfile /tmp/docker-build-push-thK9oA/iidfile --cache-from silex/nix:latest --cache-to type=inline --pull --push .
and to me it's the same command as the one that is working except theiidfile
argument.The problem is the same as https://github.com/docker/buildx/issues/177, namely that only the manifest gets pushed:
So, is there a way to disable
iidfile
?