can't select Python environment as kernel because the extension tries to write to a system path

[paciorek]

We're using the Jupyter extension on a Linux cluster, with the extension installed at the system level. (This is in the context of running code-server through Open OnDemand, though I think that is not directly relevant.)

When a user tries to select a Python environment as the kernel, nothing happens from the user perspective. In the logs, one sees that the extension is trying to create a temp directory in the system directory where the extension is installed, which the user has no permission to do.

2025-04-25 15:16:10.067 [error] Error: EROFS: read-only file system, mkdir '/global/software/rocky-8.x86_64/gcc/linux-rocky8-x86_64/gcc-8.5.0/code-server-4.91.1-rywu6um26xekdmcnat7o4xzuwfzokfls/lib/vscode/extensions/ms-toolsai.jupyter-2024.6.0-universal/temp'

Is there any way for us to configure the extension to only write to /tmp or to some directory in the user's home directory?

[DonJayamanne]

I don't think this will impact on selecting a Python kernel.
You are using an old version of Jupyter extension, please can you install the latest version along with the latest version of VS Code and Python extensions, and try again.