Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
DockerHub
Build It
docker build -t metabase/druid:0.17.0 .The build logic ingests the data in rows.json by executing the ingestion spec task task.json. This is done in the script ingest.sh; tweak as needed.
Why ingest data as part of the build process? In some cases ingestion and indexing can take 10 minutes, on top of using an obnoxious amount of memory. Better to do it during build so we can use the image right out of the box instead of making CI super slow.
Use It
docker run -p 8081:8081 -p 8082:8082 -p 8888:8888 -it metabase/druid:0.17.0Env Vars
For running Metabase tests you shouldn't need to change any of these.
CLUSTER_SIZE-- Druid config to use. Currently one ofnano-quickstart,micro-quickstart,small,medium,large, orxlarge. Default:nano-quickstartSTART_MIDDLE_MANAGER-- whether to start the middle manager process. Defaultfalse, because the middle manager is only needed for ingesting rows. Set totrueif you plan to ingest more data.ENABLE_JAVASCRIPT-- whether to enable javascript on the Druid cluster. Metabase requires this, so by default it ittrue. Set it to something besidestrueto disable it.LOG4J_PROPERTIES_FILE-- Log4j2 config. By default,/druid/apache-druid-0.17.0/log4j2.properties, copied when building the Docker image, but you can mount a directory and supply a different file if you want different logging levels.
Push It
docker push metabase/druid:0.17.0