On Nov 12 2020, at 5:59 am, vishal sharma <vish...@gmail.com> wrote:
> When we login on jupyterhub , a POD creates . but if we log out pod deleted ,
> Why it deleted ?

Without knowing anything about your configuration, my first guess would be that 
shutdown_on_logout [1] is set to be true.
[1] 
https://jupyterhub.readthedocs.io/en/stable/api/app.html#jupyterhub.app.JupyterHub.shutdown_on_logout
>
> When we login again from same credentials , again same new pod created but it 
> did not have previously downloaded modules although it is using same pvc
>
> For example :
> I installed pandas as below in notebook.
> pip install pandas
> Next day , when i opened it with same credentials , pandas module was not 
> present .

I'm assuming, based on references to a pod and a pvc, that you're running 
JupyterHub on Kubernetes. Is that correct?
If so, the usual configuration is to mount the persistent volume as the user's 
home directory. If that's what you've done, only changes to the home directory 
will persist; changes to any other part of the filesystem will be lost when the 
container stops. If your Python system is set up to install packages someplace 
other than the user's home directly, those will be lost when the pod shuts down.
If you're trying to solve this in general, you'd need to adjust your singleuser 
image to make installs go somewhere in the home directory. But if you're just 
trying to solve it for you, I'd recommend making a virtual environment in your 
home directory and installing the packages you need within that virtual 
environment. (Note that you can install and register an ipython kernel within 
that environment, so that you can run notebooks within it.)
Hope that helps,
Robert

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/8108BC62-5213-4CE0-A72E-BAE01C191401%40getmailspring.com.

Reply via email to