Hello,
I have a very specific problem for a shared VM (Ubuntu 24.04) running jupyter lab. Multiple users have access to the VM, and they share a home folder. This shared home folder is creating issues regarding permissions. The first user is able to start a lab session, using jupyter lab --no-browser --port=8888. However, if a second user then wants to start jupyter at a later point, some files are preventing that user from being able to launch jupyter.
The problem is with files within ~/.local/share/jupyter. Specifically runtime folder, nbsignatures.db, and notebook_secret. These files are created with permissions only for the first user, even when umask 002 is set for all users. I even tried with ACLs in order to have some overwriting permissions defined for the whole ~/.local/share/jupyter folder, but jupyter is still able to enforce stricter permissions. The current workaround is to chown these files to the user wanting to run, but I would like to avoid having to do that for every time another user wants to run.
My question is then if there is a way to retain my environment (multiple users, one home folder), and still have jupyter allow this. I know multiple home directories and a shared notebook directory is the preferred solution, but this environment is for students with little knowledge of Linux, so I would prefer to keep the overhead as low as possible for them, and a shared home folder is then preferred for me.
Thanks in advance!