-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ECR] [Tags]: immutable image tags #169
Comments
Hello all , we create two tags for the image where one is latest and another is Jenkins build number but with recently released tag immutability where we enabled for repo seems to be latest tag is not being tagged to the recent image as it not able to overwrite . Any one faced similar situation |
@yrsurya that's the all point if immutable tags. |
I was in a impression that image which pushed recently will be getting latest tag by default. Is there any way we can get that(latest) by default after enabling immutable option on ECR as we use latest tagged base images for the application to built on top of FROM xxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/corretto11:latest |
@yrsurya You could use the cli to untag latest before tagging your new image. https://docs.aws.amazon.com/cli/latest/reference/ecr/untag-resource.html |
We have the same issue with the |
The link @therealppa suggests is not working for me. Is it possible that it refers to some other type of tags, like aws resource tags, but not really docker container image tags? |
@pablote Looking at the description, you're probably right. According to https://stackoverflow.com/questions/56299191/remove-tag-from-image the correct command should be |
After an image tag is pushed to a repository, prevent a user from pushing an update that points the tag to a different image. This feature can be used to ensure that an image tag such as "2.1.1" refers to the same content over time. Such tags can be easier to use than the longer image digest.
An example of the pros and cons of using mutable image tags can be found here.
The text was updated successfully, but these errors were encountered: