The extension does not work on Centos 7

[trungklam]

I'm using VSCodium latest version and tried to connect to Centos 7 (7.9) and get the below error from server side

/root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node: /lib64/libm.so.6: version GLIBC_2.27' not found (required by /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node) /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node: /lib64/libc.so.6: version GLIBC_2.25' not found (required by /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node) /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node: /lib64/libc.so.6: version GLIBC_2.28' not found (required by /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node) /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node: /lib64/libstdc++.so.6: version CXXABI_1.3.9' not found (required by /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node) /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node) /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node: /lib64/libstdc++.so.6: version GLIBCXX_3.4.21' not found (required by /root/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401/node)

I guess it can come from the node version we build the extension from. I'm really appreciate if there are any workaround for this
Thanks a lot !

[lex-ibm]

This issue should be filed against VSCodium.

[trungklam]

Okay, I forwarded this issue to VSCodium as well. Perhaps I will keep this open till we got the some more hints.

[GitMensch]

I've solved this for the centos7 nodes by trying to connect with this extension (installs the not-working codium-server), then did a plain ssh into that machine and replaced node installed within it, then retried connection - works.

all steps after ssh:

$ ls -lt ~/.vscodium-server/bin/*  # get the server version hash
$ VSC_BIN=~/.vscodium-server/bin/08e6c15293922dd53a864bb041be381322fee401  # the newest one I've seen above
$ $VSC_BIN/node --version  # fails
$ ldd -v $VSC_BIN/node   # some details showing the broken glibc version
$ cd /tmp
$ wget https://unofficial-builds.nodejs.org/download/release/v18.16.1/node-v18.16.1-linux-x64-glibc-217.tar.xz
$ tar -xvf node-v18.16.1-linux-x64-glibc-217.tar.xz
$ cp -p node-v18.16.1-linux-x64-glibc-217/bin/* $VSC_BIN/
$ $VSC_BIN/node --version  # runs
$ ldd -v $VSC_BIN/node   # some details showing the working glibc version
$ cp -pr node-v18.16.1-linux-x64-glibc-217/lib/node_modules $VSC_BIN/  # this may be unnecessary

More details and "work in progress note" at VSCodium/vscodium#1629

[jeanp413]

As others have mentioned this is a vscodium issue, but starting from next release 1.86 official vscode will drop support too microsoft/vscode#201129

[GitMensch]

Yep - and the solution there is the same.

[jeanp413]

Not sure it's the same, right now only the node binary is the issue, after next release native modules will require GLIBC >= 2.28 too

[GitMensch]

Ah, so the node modules that are directly from vscode may need a recompile, too, if they are not linked against node libraries but libc.

[jeanp413]

yep