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 this doesn't lead to double the storage usage in ACR, if the system is smart enough to know that both tags refer to the same physical image, then I don't care.

but I don't know if that is the case. Anyone?

docker storage is based on layers - if you have multiple tags for an image but the base layers are the same, you will only be billed for those unique layers:
<https://forums.aws.amazon.com/thread.jspa?threadID=252188>

IIRC the 2 tags it creates are:
• 1 you control (i think?)
• 1 pulumi generates to be guaranteed to be unique

also that means you can build for example a new app docker image for each build of some pipeline, but if they all share the same base layer, you won't pay for that base layer multiple times

ah, then I have no reason to worry - thank you!