search

jeanp413 / open-remote-ssh

VSCode Remote Development: Open any folder on a remote machine using SSH.
MIT License
288 stars 40 forks source link

HOW TO: fix glibc not found errors #133

Closed Icemole closed 8 months ago

Icemole commented 8 months ago

I struggled on and off for a solution to this issue, and I found it myself by going deep into the rabbithole :) detailed instructions:

  1. Download the tar.gz found here, and extract it.
  2. Take note of the path to the log in the Output > Remote - SSH tab. The specific line must look something like logFile==/home/user/.vscodium-server/.<id>.log==.
  3. Copy the bin/node and the node_modules/* into /home/user/.vscodium-server/bin/<id>.
  4. Kill any existing connection in the remote (use htop).
  5. Try to log in again.

I got the connection working through these steps. If you can't log in, check again the log file in step 2. There should be more relevant logs other than glibc version not found.

Explanation: it seems that VSCodium's latest versions (1.81+?) use an updated node which doesn't support glibc < 2.28 (not sure about the exact numbers). See here, and delve deep into the attached issue there (in which the real fix is proposed, instead of this workaround).

[@jeanp413] Hi, this is an vscodium issue, see VSCodium/vscodium#1634, you can workaround by following this comment VSCodium/vscodium#1634 (comment)

I believe this might be the specific workaround needed to fix #131, #123 and #114 (edit: #30 and #24 have the same error message as I had).

Edit: not sure if this is the right way to do this, but if there's some better way please let me know.