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.

possible to disable labextensions?

See original GitHub issue

I’ve been doing some repo2docker development recently, which means that the base conda environment is getting installed a lot. The big frustration in this process has ben that roughly half (or more) of my build time is spent in jupyter labextension install jupyter-offlinenotebook. That’s more than two minutes per build (see #919 for an example breakdown of timings). I recognize that this is something most real users won’t see since this layer will often be cached, but it’s been pretty devastating for my development cycle.

Is there any way that we can cache labextensions separately, or make them optional? This is a useful extension for Binder, but it’s really not beneficial and extremely costly for local repo2docker.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

manicscommented, Oct 1, 2020

https://github.com/jupyterhub/repo2docker/issues/868 is probably the best solution if it can be implemented, since in theory you could completely disable jupyterlab and notebook.

1reaction

manicscommented, Sep 18, 2020

Longer term options:

Get rid of the build step with jupyterlab modules: https://github.com/jupyterlab/jupyterlab-module-federation
Allow the Jupyter UI environment to be managed separately from the execution environment, so for instance we could have a way to define which extensions are installed or not: https://github.com/jupyterhub/repo2docker/issues/868

Short term fix: maybe a docker environment variable that activates a “development” mode and skips the build step?