Hi, I see that the

@pulumi/docker

package can be used to build docker images and then push them to e.g. an

ecr

registry or it could pull images from remote registry however I’m wondering: Can I also just push images that I have build locally outside of pulumi? How would I do that? I’d like to have a build that looks like this:

- build my docker images using other tooling
- pulumi up

@pulumi/docker

is using the terraform docker provider (https://registry.terraform.io/providers/kreuzwerker/docker/latest/docs) and it doesn't look like that supports just pushing built images to a registry.

Okay, thanks

So it might make sense in some cases to have a shared stack for setting up ECR, and then have another stack setup the functions and just refer to the first stack with StackReferences. Other cases it would make more sense to just do everything in one stack. In either case it's not ideal having to do the push to ECR outside of pulumi. That's a bad limitation of the docker provider 😞 Some workarounds you could try. Use the command provider to call your scripts that do the image build and add the push logic to those scripts. Or try using a dynamic provider and use your languages docker SDK to push to ECR. Also do consider raising an issue at https://github.com/pulumi/pulumi-docker with this issue.

Okay, thanks for pointing to these resources. The reason I think I have to use two stacks is: The push only works when the ECR repository exists. As I see adding or removing a new ECR repository and lambda function as a regular activity, not just an initial bootstrap step, I thought this would have to happen first.

The push only works when the ECR repository exists.

It should be possible to depend on the ECR repository being created before running the command steps, just add it to the depends_on list.