Skip to content

AWS ECS Fargate is using digest instead of image tag

1

Hi, we pushed a new image to the ecr with the "latest" tag, like many times before. After that, our systems didnt start properly, because it didnt found the image.

CannotPullContainerError: pull image manifest has been retried 1 time(s): failed to resolve ref xxxx.dkr.ecr.eu-central-1.amazonaws.com/stuff@sha256:hash: xxxx.dkr.ecr.eu-central-1.amazonaws.com/stuff@sha256:hash: not found

Which is correct, since that image with said digest-hash isnt there anymore. After "Force new deployment" it works. Anyone any ideas how to prevent this? I know that this is aws doing with their new update, but in our dev environment, we use latest since we deploy like multiple images daily... and cant update the image tag in our terraform environment everytime.

asked a year ago2.4K views
1 Answer
0

As you correctly mentioned, this behavior is the result of the recently announced feature - Amazon ECS now enforces software version consistency for containerized applications.

As of now there is no way to disable this behavior. I suggest you follow and provide your feedback to this github issue.

AWS
EXPERT
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.