Jupyter Hub - termnal /etc/profile.d/*.sh file not sourcing

[Jegan]

Hi All,

I am running JupyterHub as a container and keeping a couple of scripts under /etc/profile.d/*.sh. When I start a new session or open a terminal, my scripts are not loading. However, while doing SSH to my container via CLI, I see the scripts are working fine.

I want to know what is stopping the scripts from running in the JupyterHub terminal. If there is any solution, please let me know to overcome this issue.

[manics]

Profile scripts aren’t always read when launching a non-login shell. See

Jupyter server source script on launch

Definitely possible. JupyterHub’s Spawner.cmd only requires that it eventually launches jupyterhub-singleuser (or one of a few equivalents like jupyter-labhub). The standard way to do this, and one that I think gives a nice experience, is to create a launcher script like: #!/bin/bash -l # set any additional environment variables / do other startup # finally, 'become' jupyterhub-singleuser exec jupyterhub-singleuser "$@" The bash -l starts a login shell, so it should be fully configured with…

for an example of how to work around this.