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

Bug running jupyterlab in Docker - "Bad config encountered during initialization" #6630

Closed
morrisalp opened this issue Nov 19, 2022 · 1 comment
Labels
status:Needs Triage Applied to issues that need triage

Comments

@morrisalp
Copy link

morrisalp commented Nov 19, 2022

When running jupyter-lab in Docker I encounter the following error:

[C 11:15:44.783 LabApp] Bad config encountered during initialization: The 'contents_manager_class' trait of a LabApp instance expected a subclass of notebook.services.contents.manager.ContentsManager or jupyter_server.contents.services.managers.ContentsManage, not the JupytextContentsManager JupytextContentsManager.

I've reproduced a minimal Dockerfile below - reproduce with docker build -t testimg . and docker run testimg.

It appears that this bug is due to Jupyterlab looking for the config file in the wrong location, because it is fixed when adding the flag --config=.jupyter/nbconfig/tree.json (docker run --entrypoint jupyter-lab testimg --config=.jupyter/nbconfig/tree.json --allow-root).

This is on Jupyterlab version: 2.3.2 (docker run --entrypoint jupyter-lab testimg --version)


Dockerfile reproducing the bug:

FROM nvcr.io/nvidia/pytorch:22.10-py3
WORKDIR /root
RUN pip install --upgrade pip \
    && pip install jupyterlab
ENTRYPOINT jupyter-lab
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to issues that need triage label Nov 19, 2022
@RRosio
Copy link
Collaborator

RRosio commented Dec 1, 2022

Hi @morrisalp, thank you for submitting this issue! Since this is an issue when you run JupyterLab this issue would be better addressed in the JupyterLab repository. If you would please try opening this issue in the Jupyterlab repository? It would also be good to try this with a more recent version of Jupyterlab if possible. Thank you

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:Needs Triage Applied to issues that need triage
Projects
None yet
Development

No branches or pull requests

2 participants