You can create ssh.bat file under windows with the content: C:\Windows\system32\wsl.exe ssh %* And then set VS Code setting “remote.SSH.path” to point to that bat file. You’ll have the same ssh configuration and credentials in VS Code as you have in WSL.
I found much better & simple answer thanks to this post. Simply create new script file named code with below contents & put file under any folder from $PATH. (echo $PATH to see what folders you can use) #! /usr/bin/env zsh local max_retry=10 for i in {1..$max_retry} do local script=$(echo ~/.vscode-server/bin/*/bin/remote-cli/code(*oc[$i]N)) if [[ -z ${script} … Read more
After a while, I found a solution that can be useful to others. In VS Code press: CTRL + SHIFT + P Type or select the option: Remote-SSH: kill VS Code Server on Host… Select the host name: And after this procedure, try connecting again to the host. That worked for me.
From my practice, you can delete the .vscode-server directory to free space. Next time you log in to this server, the system will automatically install another .vscode-server which tends to be much smaller than the original one.
Simply start a tmux process in the remote terminal start Jupyter in the tmux session. You can go out of the tmux session without closing it. In VSC you can choose the tmux session as the host.
I resolved this problem by switching to the remote server’s Docker context on my local machine: docker context create some-context-label –docker “host=ssh://user@remote_server_ip” docker context use some-context-label docker ps # A list of remote containers on my local machine! It works! After that: Connect via Remote-SSH to the container server Right click relevant container -> the … Read more
Try to kill vs code-remote host through the command after pressing ctrl + shift + p and enter Remote-SSH: kill VS Code Server on Host… Then choose your host
It was a problem with the config file. The VSCode needs the “absolute” path. In case of MacOS, ssh-copy-id seems to only copy the absolute path relative to the user. In other words, it omits “/Users/username” before “/.ssh“. Adding “/Users/username” in the IdentityFile attribute in .ssh/config solved the problem.
This has been worked out in the new version of vs-code here here, change the variable remote.SSH.serverInstallPath through settings. Example (from tankahabir’s comment) “remote.SSH.serverInstallPath”: { “work”: “/test/location”, “home”: “/foobar” }
You can remove or edit it by editing .ssh/config file. Hope this helps.