My (Gitlab)CI is building containers using Dockerfiles. To use Pull-Through-Cache rules with ECR, how should I modify it? 1. Adapt the Dockerfile's FROM: statement? For instance from FROM:php:fpm to FROM:.dkr.ecr..amazonaws.com/library/php:fpm ? But that's cumbersome (people who don't have ECR access can't build the Dockerfile) 2. Or is there any other way (in Docker config?)

ECR / Pull-through-cache rule: how should I adapt my CI?

My (Gitlab)CI is building containers using Dockerfiles. To use Pull-Through-Cache rules with ECR, how should I modify it?

Adapt the Dockerfile's FROM: statement? For instance from FROM:php:fpm to FROM:<aws_account_id>.dkr.ecr.<region>.amazonaws.com/library/php:fpm ?

But that's cumbersome (people who don't have ECR access can't build the Dockerfile)

Or is there any other way (in Docker config?)

トピック

コンテナ開発者用ツール

タグ

Amazon Elastic Container レジストリ (ECR)CI/CD Tools コンテナ

言語

English

Paul Santus - TerraCloud

質問済み 2ヶ月前148ビュー

1回答

新しい順
投票が多い順
コメントが多い順

承認された回答

Unfortunately our implementation does not leverage the Docker config "registry-mirrors" feature. This means you currently can only use our ecr pull-through cache by updating the base image reference("FROM:...").

How often do you change your Dockerfile? Is it maybe a feasible approach to use a tool like "sed" in the CI/CD to overwrite the "FROM" Reference in the Docker File to the ecr pull-through cache address, so that GitLab CI uses the cache, but other Developers who build locally don't?

Bent

回答済み 2ヶ月前

エキスパート

Oleksii Bebych

レビュー済み 2ヶ月前

Paul Santus - TerraCloud
2ヶ月前
Thanks :)

At least, now it's documented. Maybe it could be an addition to the ECR pull-through-cache feature documentation ? (together with https://repost.aws/questions/QU8MCA6JSPRBuY-xLU880atw/ecs-cannotpullcontainererror-when-using-ecr-pull-through-cache-rule )

ECR / Pull-through-cache rule: how should I adapt my CI?

関連するコンテンツ