Since I accidentally injected some confusion I'll take it a step further. We have doubly hermetically sealed environments. one docker file for the Build and then it copies over to a minimalist image for the final deployable image (using FROM and COPY --from ) .
Some of our tests are docker based as well to make sure there are not conflicts in different places it might be run. On Tue, Feb 19, 2019 at 7:47 AM Don Bowman <d...@agilicus.com> wrote: > On Mon, 18 Feb 2019 at 19:14, Gaurav Bhatnagar <gaura...@gmail.com> wrote: > > > I have been thinking if automated scripts can be provided to end users in > > Druid for "Additional Dependencies" for user initiated installation and > > configuration of optional dependencies to avoid licensing issues. Later > > these scripts can be integrated in admin UI as configuration wizards. > > > > > > > Personally I think this is the opposite way the universe is going. > People want 'hermetic' images w/ read-only filesystems, named by a single > tag or SHA hash. This is what the container universe is about. > There's some work to do in druid (e.g. middlemanager logs) to improve this > (it currently logs into files in there rather than stdout by default, and > expects that elsewhere). > > w/ a product of the scale of druid, its unlikely to be targetted @ 'small' > deployments. >
