Jupyter notebook failed to launch on remote: NoPermissions

[gandroz]

Environment data

• VS Code version: 1.60.2
• Jupyter Extension version (available under the Extensions sidebar): ms-toolsai.jupyter-2021.8.2041215044
• Python Extension version (available under the Extensions sidebar): 2021.9.1246542782
• OS (Windows | Mac | Linux distro) and version: CentOS (host) / Windows (client with remote extension)
• Python and/or Anaconda version: python 3.9
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
• Jupyter server running: Remote

Actual behaviour

Jupyter server unable to start due to file permission

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

1. Start VSCode on the Windows local machine
2. Start remote session over SSH to a CentOS machine
3. Install python and jupyter extensions(for vscode v1.60.2) on the remote CentOS machine
4. Create a new blank notebook
5. Select proper kernel (from the venv)
6. Run a cell

Logs

[DonJayamanne]

Looks like the tmp folder is not read write. Do you have permissions to allow read/write access to this folder. We create a few temporary files when running jupyter & the kernels.

[DonJayamanne]

YOu can find some solutions here https://www.thegeekdiary.com/unix-linux-what-is-the-correct-permission-of-tmp-and-vartmp-directories/ & https://unix.stackexchange.com/questions/71622/what-are-correct-permissions-for-tmp-i-unintentionally-set-it-all-public-recu

Please let me know if that works (providing access to those temporary directories)

[gandroz]

folder /root/tmp is already opened to all, but jupyter extension is still unable to create the directory.

[DonJayamanne]

is already opened to all, but jupyter extension is still unable to create the directory.

Not sure how that is possible. Jupyter extension runs under the context of VS Code.
Possible somethign is missing there.
Please could you print out the permissions for that folder
ls -l /root/tmp

[gandroz]

sure

and

[gandroz]

And just to be sure you got the context, vscode is run on a Windows machine to connect remotely to a CentOS machine, so jupyter is tried to be run remotely by the vscode-server (I guess)

[gandroz]

is it possible to not run jupyter as root ?

[DonJayamanne]

We don't run Jupyter under root, it's run under the same user/context that vscode server is running on the remote machine

[gandroz]

so why does the extension try to launch from /root/tmp and not /tmp or /home/user/.local/tmp or another temp directory ?

[gandroz]

I tried to go into the .vscode-server/bin/<commit_id> and launch nodejs. There I typed

const os = require('os');
os.tmpdir()

and it returns me /root/dir. It has to be noted that the vscode-server extension has been "installed" manually as the CentOS machine does not have access to internet connection. I suspect the tar.gz file has been extracted as root which causes me those troubles. Is that possible ?

[DonJayamanne]

I"m going to transfer to this VS COde at this stage as I don't know how VS Code works in SSH and the user context.