why does docker.image create two tags in my ACR? o...
# general
a
why does docker.image create two tags in my ACR? one with the tag that I actually specify, another one with the commit hash. Can I turn this off?
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?
b
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
a
ah, then I have no reason to worry - thank you!
👍 2