[
https://issues.apache.org/jira/browse/SOLR-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432530#comment-17432530
]
Houston Putman commented on SOLR-15321:
---------------------------------------
This should definitely be a blocker, but in the absolute worst case, we have a
gradle task that generates the official docker file. All we have to do is add
this to the docker-solr repo, and we are good to go.
This really isn't too hard of a problem to solve. We need to setup the
apache/solr-docker repo, and import all of the old builds that we want to still
be updated (probably just the 8x ones). Then in the release wizard, have a step
at the end that clones that repo, adds the resulting official docker image from
the RC and commits it. We don't even have to deal with a scripts repo anymore,
since that is now included in the Solr binary.
I can probably get this setup in a few weeks or so.
> Flesh out process for managing/storing "official" Dockerfiles used by
> docker-library
> ------------------------------------------------------------------------------------
>
> Key: SOLR-15321
> URL: https://issues.apache.org/jira/browse/SOLR-15321
> Project: Solr
> Issue Type: Sub-task
> Reporter: Chris M. Hostetter
> Priority: Major
>
> Assuming we (the Apache Solr TLP) do want to be the maintainer of "official"
> {{_/solr}} docker images moving forward, we need to flesh out how/where
> exactly we plan on storing/managing/maintaining the Dockerfiles that should
> be pointed to by the docker-library manifest file for solr...
> [https://github.com/docker-library/official-images/blob/master/library/solr]
> ie:
> * what replaces [https://github.com/docker-solr/docker-solr.git]
> * what process do we use to update/manage this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
