IssueRaiser

[ECR] [request]: pull through cache repositories for Google Container Registry (now Google Artifact Registry)

<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** Please add support for dockerhub and gcr registries in this new feature: https://aws.amazon.com/de/blogs/aws/announcing-pull-through-cache-repositories-for-amazon-elastic-container-registry/ **Which service(s) is this request for?** ECR **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Most images are stored in docker hub and users are getting rate limit errors all the time... **Are you currently working around this issue?** Syncing these docker hub images to gcr and ecr

Posted by runningman84 on Nov 30, 2021, 9:46 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

support (Software)

[ECR] [request]: pull through cache repositories for Google Container Registry (now Google Artifact Registry)

runningman84Nov 30, 2021, 9:46 AM

<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** Please add support for dockerhub and gcr registries in this new feature: https://aws.amazon.com/de/blogs/aws/announcing-pull-through-cache-repositories-for-amazon-elastic-container-registry/ **Which service(s) is this request for?** ECR **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Most images are stored in docker hub and users are getting rate limit errors all the time... **Are you currently working around this issue?** Syncing these docker hub images to gcr and ecr

Comments (0)

No comments yet. Start the discussion.

Comment on this issue