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

Afaik you cannot. Mixins like this do all their work in the constructor, and it's non-optional. The only solution to this that I've found is to remove the image building logic from the main Pulumi app. You can have one small Pulumi app that runs `up` if (and only if) the image needs to change. And the main Pulumi app uses whatever image is currently pushed.

This fits the build-once-deploy-many-times mantra, too. A single app managing both the build and deploy cycles is prone to problems.

they are working on a new major version: <https://github.com/pulumi/pulumi-docker/issues/436>
that should be more like a normal resource and detect changes to the docker build context etc