Hey all, I know folks are using Docker with Zeppelin, and I am trying to find a nice balance between size of images and usefulness of the image.
Basically, when I build Zeppelin, the resulting directory is quite large, 1.2GB. So the first question is, what is actually needed in the Docker Image? How can I make it smaller? At the same time, I am trying to find ways to ensure things like the Conf directory, the Logs directory etc can exist outside the container for persistence. Simple right? Well I am using some ENV variables as such "ZEPPELIN_CONF_DIR":"/conf", "ZEPPELIN_NOTEBOOK_DIR":"/notebooks", "ZEPPELIN_HOME":"/zeppelin", "ZEPPELIN_LOG_DIR":"/logs", and having the root live at Zeppelin, and having conf, notebooks, and logs be volumes mounted to external persistent storage. This is working, but what if I want to create a directory for "custom" jars, interpreters, etc, what would the easier way to do that be? I know in the Apache Drill project, they've added the concept of a "site" directory that is a bit more holistic than a "conf" directory as it allows them to add libs and keep that directory complete separated from the released jars ( https://drill.apache.org/docs/apache-drill-1-8-0-release-notes/) Is there anything like this in Zeppelin? Is there an easy way to keep customized things in a directory that is separate? Any thoughts on how you've optimized Dockerized setups for Zeppelin would be welcome! Thanks! John
