-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Remove jovyan
user from Jupyter Dockerfile
#1067
Comments
Alternative: have all users just be |
@costrouc @danlester about this, haven't we moved to keycloak for managing user files, and then we used the username as an alias in the terminal? As result, everyone would be jovyan with the same uids and different aliases... What should we do regarding cases as follow?
|
We can remove My thoughts where I'd eventually like this to go. I want this to "feel" like the user is on a genuine linux system. We run each user as a unique uid, with proper primary gid, and secondary group ids, along with a home directory in the expected location that matches their username. This is the expected "linux" behavior. We have the tooling the QHub to achieve this now (except for populating My take on why |
The main issue right now is that there are two home folders |
having |
We discussed this at our stand-up this morning and it sounds like it's a fairly straightforward fix to remove |
Closes by PR #1089 |
Describe the bug
QHub uses actual usernames instead of the conventional
jovyan
user, but that user still exists in the base Jupyterlab Dockerfile and has its own home directory in addition to the actual username: https://github.com/Quansight/qhub/blob/main/qhub/template/image/Dockerfile.jupyterlab#L11This results in some unexpected behavior when running basic commands:
/home/jovyan
folder, irrespective of userls
hit the/home/{username}
folder insteadExpected behaviour
Any and all commands should be run inside the user's
/home/{username}
folder, and/home/jovyan
should not exist.The text was updated successfully, but these errors were encountered: