Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out how to deal with JupyterHub 0.8 #423

Closed
yuvipanda opened this issue Jul 30, 2017 · 7 comments

Comments

@yuvipanda
Copy link

@yuvipanda yuvipanda commented Jul 30, 2017

JupyterHub 0.8 is going to be out soon, and it's backwards incompatible. So images with prior versions in them can't be used with 0.8, and vice versa.

What version should we install in docker-stacks? Should we provide variants? Unsure!

@yuvipanda

This comment has been minimized.

Copy link
Author

@yuvipanda yuvipanda commented Jul 30, 2017

/cc @minrk

@parente

This comment has been minimized.

Copy link
Member

@parente parente commented Jul 30, 2017

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?

@minrk

This comment has been minimized.

Copy link
Member

@minrk minrk commented Aug 10, 2017

Not in the stacks, really. But JupyterHub (DockerSpawner, really) needs to have a clear way to say at least "this image works with Hub 0.8". It's not really the stacks problem.

@parente

This comment has been minimized.

Copy link
Member

@parente parente commented Aug 11, 2017

OK to close this?

@minrk

This comment has been minimized.

Copy link
Member

@minrk minrk commented Aug 11, 2017

Yeah

@minrk minrk closed this Aug 11, 2017
@minrk

This comment has been minimized.

Copy link
Member

@minrk minrk commented Aug 16, 2017

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)

@parente

This comment has been minimized.

Copy link
Member

@parente parente commented Aug 16, 2017

I've added the above to the recipes on the wiki.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.