Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Abandoned
-
None
-
None
-
None
-
None
Description
This issue tracks PoC work experimenting with the idea of the following workflow:
For Users:
- a Dockerfile (or Dockerfile.local) in our git repo that can be used (directly or via gradle) to build docker images directly from a local solr.tgz (in the docker build context)
For Release Manager:
- The exact same Dockerfile serves as a "template" that gradle tasks use to generate a build/Dockerfile.official via some very simple substitutions to fill in ARG defaults based on the "official" solr-VERSION.tgz for this release
- This Dockerfile.official can then be committed to the docker-solr github repo (or some similar new 9.x+ repo) and can be build with a a completely empty build context – in which it downloads (and validates) the official solr-VERSION.tgz (based on the ARG values that were filled in during the release)
- Automated tests can help us "validate" that the generated Dockerfile.official will work prior to officially publishing release artifacts, by using a "mock" download server to host the local solr-VERSION.tgz file
The driving goal being that the Dockerfile used for official _/solr builds should be as close as possible to identical to the Dockerfile used for "local" builds by users – given the constraints put on us by the docker-library team.
Attachments
Attachments
Issue Links
- is related to
-
SOLR-15127 All-In-One Dockerfile for building local images as well as reproducible release builds directly from (remote) git tags
- Resolved