How are dockerspawner mounts supposed to work?

[maybewonderful]

Just an update.

Whilst having containers persist like this is a temporary solution, ideally I could use docker volumes or docker mounts to create data.

Unfortunately the docker volumes created as part of the documention on dockerspawner are stuck at root:root ownership, with no apparent way for the dockerspawner to force a change in ownership. I’ve tried dockerspawner.cmd dockerspawner.environment dockerspawn mounts and a tremendous number of different configurations of existing variables etc…

With no success.

This is a question that has been asked multiple times independently with substantial discussion. It was marked as a bug in 2017, but still has yet to be resolved. (I cant find this discussion again unfortunately)

here are some of the relevant discussions off hand.

Folder Permissions

I am using Azuread as the oauth for jupyterhub and I have created a folder “user-data” in the home directory of the user account for server. I have also set the create_kwargs as seen below to the user account UID. c.DockerSpawner.extra_create_kwargs = { "user": "1000", # Can also be an integer UID } The user-data folder is set to 1000 as owner and group. Whenever I login and start the container the user folder gets created as root:root under the “user-data” folder. Am I able to use the h…

Problem with DockerSpawner volumes

Hi Guys! Nice to meet you all here. I have a problem with permissions for user volumes. They are being created with root:root ownership and user does not have permission to write there. def create_dir_hook(spawner): username = spawner.user.name # get the username volume_path = os.path.join(‘/volumes/jupyterhub/’, username) print(f"Checking if {volume_path} exists…") if not os.path.exists(volume_path): print(f"{volume_path} does not exist. Creating directory...") # create a dire…

Permission Denied for new user volumes with custom path

Dockerspawner and volumes from host

I’ve struggled for a few days to get persistent data to work when using Dockerspawner and need some pointers in where I’m going wrong. I’m also using LocalAzureAdOAuthenticator, which I’ve got running. tl;dr: using the config below I get Permission denied when trying to create a Notebook in my user container. c = get_config() import os import shutil import subprocess from oauthenticator.azuread import LocalAzureAdOAuthenticator from tornado.log import app_log from traitlets import default cl…

This is a recurring issue people are facing. People like to have their environments and other folders backed up. Yes some people have created scripts as a workaround. However being able to change folder and user permissions of softare, containers etc… is at least from my experience, quite basic functionality.

fortunately it seems that the issue only occurs on newly mounted folders, i.e. if the image already possesses the file/folder, then this is a non issue. However the conda/pkgs and conda/envs folder does not exist in the base image making backup and sharing of packages and environments between users quite difficult. This is something worthwhile to have in a team, as it means I can forward on my working environment, scripts, and packages to a colleague, for troubleshooting rather than having to get admin approval to create a new image each time…

I wonder if this could be put forward as a feature request. At the very least the envs and pkgs folders can be put into the base image, as virtual environments are a staple, and backing up packages has other applications also.