[BUG] - DOCKER_STACKS_JUPYTER_CMD Not Being Recognized when using JupyterHub

[Joseph Glaser]

What docker image(s) are you using?

scipy-notebook

Host OS system and architecture running docker image

RHEL 7 and 2 x AMD EPYC 7402

What Docker command are you running?

Standard commands within jupyterhub to spawn Docker Containers.

How to Reproduce the problem?

1. Build a Docker Container with desired environment.
2. Load in environment variables in main OS via env source file (including setting DOCKER_STACKS_JUPYTER_CMD to nbclassic.
3. Launch jupyterhub with desired settings in jupyterhub_config.py.
4. Log into Web Portal.

Command output

No response

Expected behavior

You would see the classic notebook interface.

Actual behavior

You get the Jupyter Lab interface.

Anything else?

No response

Latest Docker version

• I've updated my Docker version to the latest available, and the issue still persists

[Ayaz Salikhov]

DOCKER_STACKS_JUPYTER_CMD is only implemented in start-notebook.sh.
start-singleuser.sh is launching jupyterhub-singleuser. I'm not sure if jupyterhub-singleuser (and JupyterHub) supports nbclassic.

[Jeff McCarrell]

FWIW, Switching back to the classic notebook says to set JUPYTERHUB_SINGLEUSER_APP to use the classic interface as of version 2.0

[Ayaz Salikhov]

@JPGlaser could you please try setting JUPYTERHUB_SINGLEUSER_APP for your single-user image?

[Ayaz Salikhov]

I think setting JUPYTERHUB_SINGLEUSER_APP=notebook should work when using images with Jupyter Notebook < 7.
The main code can be found here.
Also, note, that you can only launch notebook, nbclassic won't work as well.

Also, this option doesn't work yet with Jupyter Notebook 7, and I created an issue for this: jupyterhub/jupyterhub#4518

When this issue is solved, I will add an if-case to our start-singleuser.sh script.