-
Notifications
You must be signed in to change notification settings - Fork 382
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
Dockerfile
based repositories fail to start up, citing "Error unpacking user from cookie"
#1622
Comments
I'm not going to close this ticket - I'll leave that up to the maintainers. We were able to fix the issue by pinning to a specific version of JupyterLab: It looks like a regression or new incompatibility between Binder[Hub]/repo2docker etc and the latest JupyterLab? Hopefully that's useful information to someone else! |
I ran into this issue as well, and can confirm that pinning to |
Bug description
Building from a repo with a Dockerfile (so this may be a
repo2docker
issue, but I don't understand it enough to know where to raise this other than here) fails to start due to "invalid/expired cookie" when "handing over" to JupyterLab/Notebook in browser.Example on mybinder.org:
https://mybinder.org/v2/gh/binder-examples/minimal-dockerfile/HEAD
I've reproduced the issue on
1.0.0-0.dev.git.2937.h0f65f33
locally too, using our own Dockerfile.Logs from the "spun up" container created by
repo2docker
(and orchestrated by Binder):On mybinder.org you get a pretty error message. On ours locally, we get the Jupyter "login" screen, asking for a token.
Providing the token (as extracted from
kubectl describe pod ...
) just bumps back to the same screen with no error. The logs contain the above.Expected behaviour
We expect the Jupyter notebook to appear!
Actual behaviour
We get a Jupyter login page asking for the token again (with no error) ... or an error page on mybinder.org.
How to reproduce
Try to start a repo with a
Dockerfile
, for example:https://mybinder.org/v2/gh/binder-examples/minimal-dockerfile/HEAD
We've tried our own
Dockerfile
too, carefully following the Binder documentation on the subject.Have tried specifying JupyterLab 3.4.8 in via our
requirements.txt
explicitly too, in case it was an incompatibility with newer versions. Same problem persists.The text was updated successfully, but these errors were encountered: