[
https://issues.apache.org/jira/browse/SOLR-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316959#comment-17316959
]
Jan Høydahl commented on SOLR-15321:
------------------------------------
I understand if docker-team don't want to git clone the entire lucene-solr repo
just to fetch our latest Dockerfile :)
So could a hybrid approach work, where we provision a {{solr-docker}} repo at
apache, that only contains final Dockerfiles and scripts in version folders.
Not all the build infrastructure and templating as now (that will be in main
repo and partly gradle). Then in README we point to the main Solr repo for how
to release.
We can use [https://hub.docker.com/r/apache/solr] as staging location to test
docker during release vote. Also nightly builds can push images up there for
easy reproduction etc:
# Nightly builds can generate SNAPSHOT Dockerfile and publish image to e.g.
{{apache/solr:9.0.0-SNAPSHOT }}
# During release, an "official" docker image is produced and pushed to e.g.
{{apache/solr:9.0.0-STAGING}} used to smoke-test release
# After VOTE has passed
## Push the Dockerfile (&Image) to {{apache/solr:9.0.0}}
## Push the Dockerfile to official {{_/solr:9.0.0}} and submit the PR (may
need a slightly different dockerfile?)
# If there are changes needed to Dockerfile as part of docker-team review,
then commit the changes to branch_9_0 first then push the changes to
{{solr-docker}} repo.
# If a fix is needed to an older image (such as 8.8.1) then patch
{{solr-docker}} repo directly
This way the master of building correct Dockerfile is in main repo and works
for "local" workflow, and it is also master for producing the official file.
Not sure how different the two needs to be though. Such as multi-stage build vs
single-stage?
> 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: [email protected]
For additional commands, e-mail: [email protected]
