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

Hello all :wave: , currently pulumi takes up a lot of time to build using docker, is there any CI/CD solution to optimize build times? We are not using github actions or such.
Pulumi rebuilds all docker images regardless of the changes we’ve made ,so is there a short/long fix for this? All options are appreciated.

I found one issue discussing something on the same lines but can’t see a solution proposed : <https://github.com/pulumi/pulumi-cloud/issues/183>

I personally wouldn't use Pulumi to build docker images unless you have a very good reason for that. I would use Pulumi to setup the infrastructure and *possibly* for deploying new versions which refer to the image registry

It depends on your setup if deploying should be within Pulumi or should it be done differently

Pulumi is not a CI tool and creating new images is the job for CI/CD

I would suggest you to use `docker.RegisteryImagewhich` which supports buildId <https://www.pulumi.com/registry/packages/docker/api-docs/registryimage/#buildid_nodejs>