lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Koster (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11245) Cloud native Dockerfile
Date Mon, 21 Aug 2017 15:02:01 GMT

    [ https://issues.apache.org/jira/browse/SOLR-11245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135259#comment-16135259
] 

Martijn Koster commented on SOLR-11245:
---------------------------------------

Most Docker users interact with docker through images hosted on Docker hub, and there is already
a "solr" Solr image there, from the "official-images" repo managed by Docker Inc. That uses
the image from https://github.com/docker-solr/docker-solr, which is managed by myself and
committer [~shalinmangar] with help from [~dsmiley] and others, and gets reviewed by the Docker
library team. It is setup as a github organisation, so that we can add users, and arrange
for succession and so on.

This image itself is fairly straightforward; it's just Solr installed in an OpenJDK image,
with some scripts to make it a little easier to work with, and some documentation to go along
with it. Most of the work goes into setting up the build process for the official images builders,
doing security verification, looking at our own Travis CI, maintaining multiple versions,
keeping on top of new versions that are released, working with the Docker library team, dealing
with github issues as they are raised, keeping up with the ever-changing Docker features and
so on. We try to be careful about backwards compatibility; this image has been around for
a couple of years now, and originally came from one I started in 2013. So far folks seem to
be happy enough with how these things are working out. 
If you want to help out there, you're very welcome; there are often github issues asking for
help and examples, and occasional new feature requests without PRs.

If there is an appetite for the Apache Solr committers/jira/infrastructure whatever to be
more involved or take administrative responsibility or whatever, I'm open to discussing that.

> Cloud native Dockerfile
> -----------------------
>
>                 Key: SOLR-11245
>                 URL: https://issues.apache.org/jira/browse/SOLR-11245
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Build
>    Affects Versions: 6.6
>            Reporter: jay vyas
>             Fix For: master (8.0)
>
>
> SOLR Should have its own Dockerfile, ideally one that is cloud native (i.e. doesn't expect
anything special from the operating system in terms of user IDs, etc), for deployment, that
we can curate and submit changes to as part of the official ASF process, rather then externally.
 The idea here is that testing SOLR regression, as a microservice, is something we should
be doing as part of our continuous integration, rather then something done externally.
> We have a team here that would be more then happy to do the work to port whatever existing
SOLR dockerfiles are out there into something that is ASF maintainable, and cloud native,
and easily testable, as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message