Now built on python-alpine.
Pre: ~2GB. Post: 163MB.
Note that I do almost everything in a single RUN command to ensure that Docker layer stays small; splitting this up makes it easy to end up > 1GB
yeah, I'd anticipate we'll have people doing: FROM dagster/dagster-py37:latest as a base image, to layer their code on top of the latest Dagster.
This Dockerfile also serves as a good reference artifact to show users how to build their own, so they can start from this and write their own if for some reason they need to further customize how they install Dagster.
I generally shy at this kind of surgery inside a Dockerfile, preferring to do it in the build context and using ADD to make it explicit what's in and what's out
Per in person discussion, we're going to do a couple things here:
(1) Remove publishing nightly Docker images; if we do publish public images, we should do so only for releases vs. the nightly build.
(2) Update all builds to use Python base images instead of the dagster public images