Open steveej opened 1 month ago
this issue occurred because my local vscodium had a setting for for a custom binary name:
"remote.SSH.experimental.serverBinaryName": "openvscode-server"
this it can be worked around by creating a symlink on the remote server.
[dev@x64-linux-dev-01:~/.vscodium-server/bin/0d01a72525276e5e3771fe5851b9c83de0de1e2b/bin]$ ln -s /home/dev/.vscodium-server/bin/0d01a72525276e5e3771fe5851b9c83de0de1e2b/bin/{codium,openvscode}-server
this isn't very convenient as it requires manual intervention on each update. i wonder whether it's worth adding an option for alternative binary names to this module.
according to the user journal the patching of the binary gets executed:
however, vscodium cannot to the remote successfully.
upon checking, the node binary is still missing a library:
i used the following config snippet for the remote machine. i tried omitting the
nodejsPackage
which hasn't made a difference.