Inclusion of redundant software about nest-docker HOT 2 OPEN

This has different reasons, (a) some requirements are required to build secondary targets like the user level documentation and (b) the image serves a versatile usage, e.g for the use in a classroom setting.
I think it would make sense to have separate images for different purposes. The overall number should remain low though. Images for laptops do not need the different MPI implementations base, as the HPC ones would, for example.

from nest-docker.

Hi, I think a bit more "granularity" in terms of features included in the images would be preferable - at least having one somewhat lightweight runtime option (nest, pynest, gsl, openmp, MPI, boost) would be nice. But I agree it shouldn't be too many. For me it would make sense to base the hybridLFPy image on such an official NEST image in that case.
As I quite often use MPI locally for testing and debugging, I wouldn't differentiate between HPC images and laptop images. But MPICH and openMPI options may be needed. JUSUF requires MPICH it seems, but other clusters may need openMPI for all that I know.

from nest-docker.