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

If you want to keep track of your upload in the Pulumi's stack/state, then maybe a LocalCommand could come in useful? <https://github.com/pulumi/pulumi-command>

I think you want

<https://www.pulumi.com/registry/packages/docker/api-docs/registryimage/>

Looking at the actual implementation of the `awsx` ecr bit may help clarify too::
<https://github.com/pulumi/pulumi-awsx/blob/master/awsx/ecr/image.ts>

is this due to pulumi's design inclination toward tracking dirty vs clean resources ?

implementation aside also trying to pick up on the overall design methodology