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

Things can get created in the repo that aren't managed by Pulumi. Which means, Pulumi can't delete them. AWS has a requirement that the repo must be empty before it can be deleted.

You either need to create all items in the repo through Pulumi (so that `pulumi destroy` knows to delete them), or else you need remove them from the repo before running `pulumi destroy`.

Aside: you don't need `pulumi.output()` there. All that does is wrap the imageName (which is an Output&lt;string&gt;) in another Output&lt;string&gt;.

<@U012UJTT55M> thanks for your reply. The thing is, my image and the ecr repo both were created through pulumi. In other stacks with similar structure, the `pulumi destroy` works perfectly. But, in some cases it doesn't work.

currently, I have to delete the image (which was created through pulumi) from aws dashboard, then use the `pulumi destroy` command.

But for other stacks `pulumi destroy` removes the repo with the images with out any issue.

This would happen if anything that isn't Pulumi is putting resources into the repo. For example, is anyone doing a `docker push`?

<@U012UJTT55M> no. I'm the sole user within the namespace. No one else can push into the repo.