search

jupyterhub / zero-to-jupyterhub-k8s

Helm Chart & Documentation for deploying JupyterHub on Kubernetes
https://zero-to-jupyterhub.readthedocs.io
Other
1.56k stars 799 forks source link

Using storage type "none" creates mysterious "work" directory #3502

Closed kkapper closed 2 months ago

kkapper commented 2 months ago

Bug description

If you are using the "none" storage type for the singleuser pods in a jupyterhub deployment you will have this directory created for you /home/jovyan/work

How to reproduce

Just use the none type for single user storage and launch a user pod.

jupyterhub:
  singleuser:
    storage:
      type: none

Expected behaviour

There would simply not be any directories created at /home/jovyan other than what extra volumes may be specified.

In the case below I am using storage type: dynamic

image

We create shared and private directories, and we get a lost+found directory auto generated (not idea but not this issue)

Actual behaviour

In this case, we are using storage type: none

image

You can see we get some kind of /home/jovyan/work directory with an odd create date.

Your personal set up

Using zerotojupyterhubk8s chart version 3.0.3

kkapper commented 2 months ago

I can't find any references to that /work directory being created by the chart so I suspect it might be a bug, although this may be intended behavior.

manics commented 2 months ago

If you haven't mounted any storage you'll see whatever is in your original container image. Z2JH doesn't provide any files or directories by default.

github-actions[bot] commented 2 months ago

Hi there @kkapper :wave:!

I closed this issue because it was labelled as a support question.

Please help us organize discussion by posting this on the https://discourse.jupyter.org/ forum. If it's your first time posting please read https://discourse.jupyter.org/t/getting-good-answers-to-your-questions/1825. The more information you provide the more likely we can help you.

Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other.

Thanks you for being an active member of our community! :heart: