From 8bdf4dd0058b853ea10ce3956ed0d30ad4b25920 Mon Sep 17 00:00:00 2001 From: Michael Blaschek <michael.blaschek@univie.ac.at> Date: Mon, 8 Feb 2021 22:15:54 +0100 Subject: [PATCH] Update vscode.md --- Editors/vscode.md | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/Editors/vscode.md b/Editors/vscode.md index 6209791..079410b 100644 --- a/Editors/vscode.md +++ b/Editors/vscode.md @@ -11,16 +11,27 @@ There is package called `Remote Development` in VSCode which includes - Remote WSL - Remote Containers -Although all might be useful, we try to make use of the first one Remote-SSH. If you want to connect to `jet01.img.univie.ac.at` that is not a problem. Works out of the box. However, using `srvx8` does not. The kernel is too old and requirements are not met. There is a fix. We are going to use a [singularity container](https://sylabs.io/guides/3.7/user-guide/) to run a more recent version of `node` and allow VSCode to use `srvx8` as well. It will complain a bit, but work. +Although all might be useful, we try to make use of the first one Remote-SSH. If you want to connect to `jet01.img.univie.ac.at` that is not a problem. +Works out of the box. However, using `srvx8` or `srvx1` does not. The kernel is too old and requirements are not met. +There is a fix. +We are going to use a [singularity container](https://sylabs.io/guides/3.7/user-guide/) to run a more recent version of `node` and +allow VSCode to use `srvx8` as well. It will complain a bit, but work. Here is how: -1. Login to `srvx8` +1. Login to `srvx8` or `srvx1` 2. run `/opt/containers/vscode-server/setup.sh` -3. Look inside `$HOME/.vscode-server/singularity.bash` and make sure that path that you require are available in `SINGULARITY_BIND` variable. Your Home directory is always available. Other system path not. - - Maybe it is necessary to change to BASH, `chsh -s /bin/bash` on remote host +3. Look inside `$HOME/.vscode-server/singularity.bash` and make sure that path that you require are available in `SINGULARITY_BIND` variable. + Your Home directory is always available. Other system path are not. + - Maybe it is necessary to change the user shell of your account to bash. Run `chsh -s /bin/bash` on remote host (`srvx8`, `srvx1`, ...) 4. Switch `remote.SSH.localServerDownload` to `off` in the Remote SSH package. -5. Setup a new host in Remote SSH on your VScode and connect to `srvx8`. +5. Setup a new host in Remote SSH on your VScode and connect to `srvx8` or `srvx1`. Configure a Python interpreter in VSCode according to the installed module: + - SRVX8 : `/home/opt/spack/opt/spack/linux-centos6-haswell/gcc-5.3.0/anaconda3-2020.07-opjqtspow2mjqthtdxvx7epz6rntkv2p/bin/python` + - SRVX1 : `/home/opt/spack/opt/spack/linux-centos6-sandybridge/gcc-5.3.0/anaconda3-2020.07-6p2eqnrd2mu4masynsdqvrbfdit7fyuk/bin/python` -`/home/opt/spack/opt/spack/linux-centos6-haswell/gcc-5.3.0/anaconda3-2020.07-opjqtspow2mjqthtdxvx7epz6rntkv2p/bin/python` +## Updates + +Whenever the vscode-server reports an error, it might have happened that it automatically updated +and a new version has been installed on the remote host. if so run `~/vscode-server/fix.sh` to make the changes to the run scripts. +Then it should work again. -- GitLab