Investigate using Docker Bake for Example Notebook Images

[thesuperzapper]

The example-notebook-servers are a tree of container images which all FROM each other, starting from a specific base.

Right now, they use a complex nest of make commands to ensure that building one image will correctly build its upstream dependencies if they have changed, otherwise it uses the cached version (either from local cache or remote).

• https://github.com/kubeflow/kubeflow/tree/master/components/example-notebook-servers#build-single-image
• https://github.com/kubeflow/kubeflow/tree/master/components/example-notebook-servers#build-all-images

I wonder if we can replicate this in a more declarative manner using dockers bake format.

THINGS TO CONSIDER:

• We want to be able to run builds in parallel where possible. That is, once the base is built, we can build the jupyter, rstudio and code-server linages in parallel. Similarly, with some of the sub images like jupyter which is the base of a few other lines (for PyTorch/Tensorflow/Scipy).
  • It's not clear if this is easier or harder with bake