You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying avoid Docker Hub rate limits by pulling base images from Amazon's Public ECR Gallery (https://gallery.ecr.aws). I know that Kaniko supports the --registry-mirror flag for using a Docker registry mirror, and I’m wondering if this flag can be used with public.ecr.aws.
So far I've tried setting the --registry-mirror flag like this
and I would expect for e.g. alpine image to be pulled from the following url: public.ecr.aws/docker/library/alpine:latest
however I get the following error instead (seems like /v2 and /manifests paths are added to the url)
WARN[0001] Failed to retrieve image alpine: from remapped registry public.ecr.aws: unable to complete operation after 0 attempts, last error: GET https://public.ecr.aws/v2/library/alpine/manifests/latest: NAME_UNKNOWN: The repository with name 'alpine' does not exist in the registry with id 'library'. Will try with the next registry, or fallback to the original registry.
Is this a supported use case for --registry-mirror? If so, I would appreciate any advice on how to fix this issue.
Thanks a lot in advance!
The text was updated successfully, but these errors were encountered:
jpilch
changed the title
Using --registry-mirror be used with Amazon ECR Public Gallery
Using --registry-mirror with Amazon ECR Public Gallery
Apr 7, 2025
Hello,
I'm trying avoid Docker Hub rate limits by pulling base images from Amazon's Public ECR Gallery (https://gallery.ecr.aws). I know that Kaniko supports the --registry-mirror flag for using a Docker registry mirror, and I’m wondering if this flag can be used with public.ecr.aws.
So far I've tried setting the --registry-mirror flag like this
and I would expect for e.g. alpine image to be pulled from the following url:
public.ecr.aws/docker/library/alpine:latest
however I get the following error instead (seems like
/v2
and/manifests
paths are added to the url)Is this a supported use case for --registry-mirror? If so, I would appreciate any advice on how to fix this issue.
Thanks a lot in advance!
The text was updated successfully, but these errors were encountered: