expectation? that I would never see maven :) so given how the plugins work, it would either need to be batteries-included (which is what I did), or would need to be a 'small'/'medium'/'large' w/ various sets of them.
given that i'm deploying in k8s, I would want the have the GCS/S3/Azure blob storage extensions available. I would expect the travis pipeline would build and publish to dockerhub **or** the dockerhub build pipeline would see the tag push to github and build automatically/label. a single image is prob fine, but it could be druid:broker, druid:ingest, .. etc. env vars to configure is OK, but better would be a configmap that it would reload via inotify when changed. i would expect the container to have a single process. that it would have 100% of the content from signed sources. mine works from distroless, i'll post it for interest. i had to build since the released bundle doesn't have the contrib extensions. I can do a proper one and send via PR as long as I understand what people want/don't want. On Wed, 16 Jan 2019 at 17:43, Charles Allen <charles.al...@snap.com.invalid> wrote: > The idea has been toyed around with internally here. What would your > expectations be of such an image? > > > On Wed, Jan 16, 2019 at 2:35 PM Don Bowman <d...@agilicus.com> wrote: > > > Is anyone working on a docker image? I mean, there are quite a few out > > there but they have some various issues, usually security based as they > > inherit from non-too-strong bases. > > > > I have done one w/ gcr.io/distroless/java as the parent, and it seems > > working, but not sure if there is a reason or strategy for not having one > > in the repo and built by travis to dockerhub. > > > > Some of us would like to be deploying via helm in kubernetes and this is > > causing it to be a bit complex. > > >
