We should definitely provide ways to build the image yourself, and in the
future use apache/solr-nightly for release candidates. But for the first
release I don't think it requires another RC.

Here is the way to build the docker image yourself:

docker build
https://dist.apache.org/repos/dist/dev/solr/solr-9.0.0-RC1-rev-4ea6ecc35c0f6585c76e0713acfe917ccfe3b8cf/solr/docker/Dockerfile.official
--build-arg SOLR_DOWNLOAD_URL=
https://dist.apache.org/repos/dist/dev/solr/solr-9.0.0-RC1-rev-4ea6ecc35c0f6585c76e0713acfe917ccfe3b8cf/solr/solr-9.0.0.tgz
-t solr-rc:9.0.0-rc1

On Tue, Mar 29, 2022 at 3:43 PM Ishan Chattopadhyaya <
[email protected]> wrote:

> I don't think anyone should attempt to vet this RC1 from that non official
> docker image (cominvent). If we want users to test the docker image, let us
> host it on docker-solr's hub (or provide steps for user to build for
> themselves and try).
>
> On Tue, 29 Mar, 2022, 11:48 pm Jan Høydahl, <[email protected]> wrote:
>
>> Please vote for release candidate 1 for Solr 9.0.0
>>
>> The artifacts can be downloaded from:
>>
>> https://dist.apache.org/repos/dist/dev/solr/solr-9.0.0-RC1-rev-4ea6ecc35c0f6585c76e0713acfe917ccfe3b8cf
>>
>> You can run the smoke tester directly with this command:
>>
>> python3 -u dev-tools/scripts/smokeTestRelease.py \
>>
>> https://dist.apache.org/repos/dist/dev/solr/solr-9.0.0-RC1-rev-4ea6ecc35c0f6585c76e0713acfe917ccfe3b8cf
>>
>> NB: Make sure to do a 'git pull' on branch_9_0 to get the latest
>> smoketester version.
>>
>> Since this is a major release I encourage a more thorough manual
>> inspection and test of the artifacts than the smoke tester alone.
>>
>> A Docker image is available at docker hub as "cominvent/solr:9.0.0-rc1"
>>
>> The vote will be open for at least 72 hours i.e. until 2022-04-01 19:00
>> UTC.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Here is my +1
>>
>> SUCCESS! [0:51:42.777256]
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>

Reply via email to