Collect and reach toward related docker images

[nthiery]

• Collect and update a list of links to related docker images
• Learn from them, and seek ways to make them consistent, in particular from the user's perspective
• Reach toward them, with the aim to tame the multiplication of SageMath (and Jupyter?) docker images out there wich is a source of confusion for the users

[embray]

On a somewhat related note, as it is we have some duplication between our own images in this repo. In particular the Dockerfiles for sagemath and sagemath-devel are almost if not exactly identical except they then install different versions of sage. Maybe I should open a separate issue for this, but I would propose a slight reshuffling:

• We add a base image that does not include sage; only its build dependencies: This is basically the same as the existing sagemath/sagemath-devel but without the installation step. I might actually call this image sagemath-develsince it's for sage development. The existing one could be renamed sagemath-latestor something.
• The existing sagemath images are then based on the above image, and are only different in what version they install.
• For sagemath and sagemath-jupyter images we should also give them version tags. Since sage is the main product here it would make sense to use the sage version, but maybe also include a patch version for updates to other dependencies (mainly jupyter). The description of the image can provide the full list of versions (all the more reason to generate the README from a template or something).

[nthiery]

On Wed, Feb 10, 2016 at 07:45:06AM -0800, Erik Bray wrote:

On a somewhat related note, as it is we have some duplication between our own images in this repo. In particular the Dockerfiles for sagemath and sagemath-devel are almost if not exactly identical except they then install different versions of sage. Maybe I should open a separate issue for this, but I would propose a slight reshuffling: * We add a base image that does not include sage; only its build dependencies: This is basically the same as the existing sagemath/sagemath-devel but without the installation step. I might actually call this image sagemath-develsince it's for sage development. The existing one could be renamed sagemath-latestor something. * The existing sagemath images are then based on the above image, and are only different in what version they install.

+1.

Maybe sagemath-dependencies for the base image?

 * For sagemath and sagemath-jupyter images we should also give them
   version tags. Since sage is the main product here it would make
   sense to use the sage version, but maybe also include a patch
   version for updates to other dependencies (mainly jupyter). The
   description of the image can provide the full list of versions (all
   the more reason to generate the README from a template or
   something).

+1