Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

JupyterLab 3.0.0a10 /lab url doesn't work

See original GitHub issue

Bug description

Normally repo2docker defaults to launching Jupyter Notebook, but you can switch to JupyterLab by changing the URL path to /lab. This fails with JupyterLab 3.0.0a10 (the latest pre-release). JupyterLab release schedule: https://github.com/jupyterlab/jupyterlab/issues/8038

Expected behaviour

Going to /lab should take you to the JupyterLab interface

Actual behaviour

You get the Jupyter 404 page:

404 : Not Found

You are requesting a page that does not exist!

How to reproduce

Click on https://mybinder.org/v2/gist/manics/922d4e88fefc6d38fccea8cd2097bc28/master?urlpath=lab Or run repo2docker https://gist.github.com/manics/922d4e88fefc6d38fccea8cd2097bc28 and go to /url

Although the default will remain JupyterLab 2.0 for the immediate future I think we should ensure 3.0 works for anyone who wants to use it (https://github.com/jupyterhub/repo2docker/issues/935)

Issue Analytics

State:
Created 3 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

blink1073commented, Sep 8, 2020

We fixed the ability to launch jupyterlab as a classic notebook extension in https://github.com/jupyterlab/jupyterlab/pull/8956 (pending another beta release). We will eventually remove this capability once everyone has migrated to using jupyter_server.

1reaction

blink1073commented, Aug 19, 2020

This is related to https://github.com/jupyterhub/jupyterhub/pull/3128. The recommended way to use JuptyerLab 3.0 with JupyterHub is to use c.Spawner.cmd=["jupyter-labhub"]