-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
How to make it work? #1
Comments
Are you connecting to localhost by any chance? That seems the only option to make this work.... |
Hi, sorry for the delay in replying! I've definitely had success with Ensure you have the |
I confirm I can run on windows with linux remote. relavant settings: local user settings (json) {
"remote.SSH.serverInstallPath": {
"apptainer~server": "~/.vscode-container/apptainer"
},
"remote.SSH.enableRemoteCommand": true,
"remote.SSH.useLocalServer": true,
"remote.SSH.remoteServerListenOnSocket": false,
} key point
my Host server apptainer~server
HostName some.ip.address
User my_user_name
Host apptainer~*
RemoteCommand source /cvmfs/cms.cern.ch/cmsset_default.sh && cmssw-el9 -B /datafs -B /publicfs -- /bin/bash -l -c
RequestTTY force key points:
Last points
Now I have new issues:
Singularity> code .
Unable to connect to VS Code server: Error in request.
Error: connect ENOENT /run/user/1001/vscode-ipc-ae29788f-ea45-4591-93b9-2b72c8cebb88.sock
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
errno: -2,
code: 'ENOENT',
syscall: 'connect',
address: '/run/user/1001/vscode-ipc-ae29788f-ea45-4591-93b9-2b72c8cebb88.sock'
}
|
In theory, this should work, but in practice it doesn't as described by a gazillion people e.g. in microsoft/vscode-remote-release#6086 microsoft/vscode-remote-release#4474 and microsoft/vscode-remote-release#1722
The root of the problem is that the
RemoteCommand
is always none. Since I trust this is working for you, I wonder how have you been able to make RemoteCommand work for you when it does not work for anybody else (including myself!)The text was updated successfully, but these errors were encountered: