You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
open the container spawned (I use microk8s in my deployment).
It is still running the lab mode, which I expect the notebook since I set DOCKER_STACKS_JUPYTER_CMD=notebook
Also run ls -al, there is no .bashrc in the user home folder.
Command output
No response
Expected behavior
The entity start at notebook mode and the .bashrc setting is not being wiped out.
Actual behavior
It is all fine if I run the container without JUPYTHERHUB_API_TOKEN by docker run in my local machine. But spawn the user by spawner, the JUPYTERHUB_API_TOKEN will shift to start-singleuser.sh (as
I'm closing this issue (actually 2 issues) - there is a solution for the first issue and it's documented, and the second one is a duplicate.
Please, let me know, if I got something wrong.
What docker image(s) are you using?
minimal-notebook
OS system and architecture running docker image
Ubuntu 18.04 amd64
What Docker command are you running?
How to Reproduce the problem?
DOCKER_STACKS_JUPYTER_CMD=notebook
ls -al
, there is no.bashrc
in the user home folder.Command output
No response
Expected behavior
The entity start at notebook mode and the
.bashrc
setting is not being wiped out.Actual behavior
It is all fine if I run the container without
JUPYTHERHUB_API_TOKEN
by docker run in my local machine. But spawn the user by spawner, theJUPYTERHUB_API_TOKEN
will shift tostart-singleuser.sh
(asdocker-stacks/base-notebook/start-notebook.sh
Lines 11 to 14 in f60eda1
Is there anything run in my
singleuser
setting?Anything else?
No response
The text was updated successfully, but these errors were encountered: