Could this derive from a list of images on the host / on a private docker registry?

[Analect]

@ryanlovett
In reviewing some of the material here, your imagespawner was mentioned, which is of interest to me. Your readme suggests, or I may be misinterpreting, that the only images that might work are the ones derived from jupyter (maybe those coming from docker-stacks). Is that the case?

It seems that, as per binder, there may be a requirement for images to derive from 'special' base images that perhaps have a certain magic sauce already in them for them to work seamlessly on jupyterhub? If so, are you aware of any way to retrofit an image so it will behave on jupyterhub?

Could you envisage a solution that might allow for any image available on the jupyterhub host machine (those visible on running docker images) to use something like this to show available images to a user to spawn ... or better still, for it to programmatically launched on a user's behalf a prespecified image that is known to exist or that can be easily cloned from a git repo ... something akin to what binder is doing ... but without all the kubernetes bells and whistles?

Thanks.