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

hey, Docker images are immutable and repeatable, so you should just the the pulumi image resource
<https://www.pulumi.com/docs/reference/pkg/docker/image/#registry_nodejs>
This'll push to a registry if it's been tagged with a repo name, and if the image has already been built, Docker won't do anything, it'll just use the already built image and push to the repo for you

bit more context:
if you have an image built locally called `aws_account_<http://id.dkr.ecr.region.amazonaws.com/my-web-app:v0.1|id.dkr.ecr.region.amazonaws.com/my-web-app:v0.1>`

and then in pulumi you define an image like so:

```new docker.Image("my-image",
  imageName: <http://aws_account_id.dkr.ecr.region.amazonaws.com/my-web-app:v0.1|aws_account_id.dkr.ecr.region.amazonaws.com/my-web-app:v0.1>```
Docker won't build a new image, because the pulumi provider uses the docker library, and docker already knows it exists