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
Please vote on this issue by adding a 馃憤 reaction 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
Tell us about your request
We would like to use pull through cache with elastic public registries.
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?
Would like to add a pull-through cache rule for docker.elastic.co public registries to allow a single source for container images (ECR).
Are you currently working around this issue?
We are currently unable to use pull through cache with docker.elastic.co registries as it is not yet supported as an upstream source registry.
Additional context
The Elastic Registry is public and does not require credentials.
Community Note
Tell us about your request
We would like to use pull through cache with elastic public registries.
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?
Would like to add a pull-through cache rule for docker.elastic.co public registries to allow a single source for container images (ECR).
Are you currently working around this issue?
We are currently unable to use pull through cache with docker.elastic.co registries as it is not yet supported as an upstream source registry.
Additional context
The Elastic Registry is public and does not require credentials.
Attachments
https://www.docker.elastic.co/
The text was updated successfully, but these errors were encountered: