[
https://issues.apache.org/jira/browse/SOLR-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404555#comment-17404555
]
Houston Putman commented on SOLR-15598:
---------------------------------------
I think this is a very good thing to think about. I'm not sure how the AWS
public image registry works with regard to official images or
multi-architecture images (which both Solr and the Solr Operator use), so some
investigation needs to be done before we go down this route.
It also looks like github has a public image registry as well, if we want to
distribute the image across all options. I don't think Azure, GCP or any of the
other cloud providers have something similar. It looks like they only support
private image registries.
> Push docker images to major public docker image registries
> ----------------------------------------------------------
>
> Key: SOLR-15598
> URL: https://issues.apache.org/jira/browse/SOLR-15598
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Docker
> Reporter: Tim Terlegård
> Priority: Trivial
>
> The solr docker image is now pushed to dockerhub. My wish is that the Solr
> and Solr Operator images are also pushed to other major public docker
> registries.
>
> I host Solr in AWS. AWS has a public docker image registry. If that image
> registry had the Solr and Solr Operator images I could just use them. Because
> they don't exist there I pull the images from dockerhub and push them to my
> own private image registry in AWS. Dockerhub has rate limiting on pulls which
> is one reason why I want the image in AWS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
