Skip to content
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.

Sign up for GitHub

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

Jump to bottom

workspaces confusion problem #15989

Closed
rickmody opened this issue Mar 13, 2024 · 2 comments
Closed

workspaces confusion problem #15989

rickmody opened this issue Mar 13, 2024 · 2 comments
Labels
bug status:Answered The issue has been answered by a community member. status:Closing as Answered The issue will be closed soon as answered unless there is further follow-up. status:Needs Triage Applied to new issues that need triage Tag:Workspaces

Comments

@rickmody
Copy link

Hello, Jupyter developer. I'm currently facing an issue. I'm launching N Jupyter containers, all of which mount directories from the home directory of the same user. This has caused confusion with workspaces. The default location for JupyterLab workspaces directory is $HOME/.jupyter/lab/workspaces/. How can I isolate this directory? Are there any parameters for configuration?
@rickmody rickmody added the bug label Mar 13, 2024
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label Mar 13, 2024
@krassowski
Copy link
Member

You can set different JUPYTERLAB_WORKSPACES_DIR for different users see https://jupyterlab.readthedocs.io/en/latest/user/directories.html#jupyterlab-workspaces-directory

@krassowski
Copy link
Member

You can also set this via LabApp.workspaces_dir traitlet if that's easier.

Loosely related to #11120

@JasonWeill JasonWeill added the status:Answered The issue has been answered by a community member. label Mar 19, 2024
@JasonWeill JasonWeill mentioned this issue Mar 19, 2024
Open
@JasonWeill JasonWeill added the status:Closing as Answered The issue will be closed soon as answered unless there is further follow-up. label Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug status:Answered The issue has been answered by a community member. status:Closing as Answered The issue will be closed soon as answered unless there is further follow-up. status:Needs Triage Applied to new issues that need triage Tag:Workspaces
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@krassowski @JasonWeill @rickmody