Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
The mantra here has always been to update to support the latest upon the request (https://github.com/jupyter/docker-stacks#stacks-tags-versioning-and-progress). If a user needs support for a prior version, she can pin to any of the image tags prior to the version bump (https://github.com/jupyter/docker-stacks/wiki/Docker-build-history).
Is there a reason to handle jupyterhub differently?
For anyone who finds this while looking for upgrade info: The fix is to make sure that the same version of jupyterhub is installed in your image as the Hub itself.
In general, this is enough:
FROM jupyter/base-notebook:5ded1de07260 RUN pip install jupyterhub==0.8.0b1
(with the appropriate base image and jupyterhub version for your deployment)