No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I bumped my head on this a few months ago, but I never really fully documented my solution (the workaround I did at the time was to push the image to docker hub and have my pulumi program pull that image, but that isn’t really a great solution)

This isn’t a solution by any means, but we can keep hacking on it.

It might be helpful to post this to <https://github.com/pulumi/pulumi/discussions> as I’m sure more folks will come up with this problem and it won’t get lost in slack backscroll then!

thanks <@U01SX9Z1412> I'll do that :slightly_smiling_face:

once you’ve done that, we can also open an issue on <https://github.com/pulumi/pulumi-docker> which is where we would need to add buildx support!

thank you for posting the discussion! the issue that was filed is at <https://github.com/pulumi/pulumi-docker/issues/296> as well!

thanks I've added a few comments, I think the underlying issue is that when you spawn a process in node you end up using 'standard docker' and not 'docker buildx' ...