Closed zeroxia closed 4 days ago
If it can help: make sure you use the latest remote-ssh version (Remote-SSH version: remote-ssh@0.110.1
), I got bite by this too. After, I got stuck at "Downloading VS Code Server ...", it took ~5 minutes for the download to start. Now it's ok.
Updating Remote-SSH to v0.110.1 does not fix this and seems like a regression. If this is intentional, it is contrary to the Feb 2025 deadline communicated here: https://code.visualstudio.com/docs/remote/faq#_can-i-run-vs-code-server-on-older-linux-distributions
On Ubuntu 18.04, I built the glibc-2.28 and install it to /opt/glibc-2.28, just like this post describes:
Reference: https://stackoverflow.com/a/77247394/2298014
When you do building, you should do it in a standalone "build" directory:
mkdir ~/src
cd ~/src
wget 'https://ftp.gnu.org/gnu/glibc/glibc-2.28.tar.gz'
tar xzf glibc-2.28.tar.gz
mkdir glibc-2.28-build
cd glibc-2.28-build
../glibc-2.28/configure --prefix=/opt/glibc-2.28
make
# make sure you can write to /opt/glibc-2.28
make install
Then after installing the package "patchelf":
# version "5c3e652f63e798a5ac2f31ffd0d863669328dc4c" is currently remote-ssh downloads and it depends on GLIBC_2.28
cd ~/.vscode-server/bin/5c3e652f63e798a5ac2f31ffd0d863669328dc4c
cp node node_bak
patchelf --set-interpreter /opt/glibc-2.28/lib/ld-linux-x86-64.so.2 --set-rpath /opt/glibc-2.28/lib:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu node
# Now it runs:
./node
v18.18.2
With this patch, v1.88 is working with my setup for now.
But this is obviously very cumbersome and fragile. Next time vscode server updates, you need to do patchelf for the new "node" binary.
And it is sad to know after Feb 2025, the systems with < GLIBC_2.28 will be unsupported.
@zeroxia based on the logs you are using an older ssh extension, can you update to the latest and see if the issue persists. We have updated how the server is downloaded in v1.88 as part of https://github.com/microsoft/vscode/issues/206790 and it will only work with extension version >= 0.110
@code-ghalib can you share the logs from ssh extension.
@deepak1556 there were no logs in the extension host folder because it looks like it was the dev containers extension that failed - updating that to v0.354.0 has fixed the issue, thanks!
Can confirm that v0.354.0 of dev containers extension fixed things for me as well!
@zeroxia based on the logs you are using an older ssh extension, can you update to the latest and see if the issue persists. We have updated how the server is downloaded in v1.88 as part of #206790 and it will only work with extension version >= 0.110
My VS Code can't see v0.110, it only sees v0.109 as the latest.
Do I need to "switch to prerelease version"?
Can you check if you have extension updates disabled in your settings ?
Can you check if you have extension updates disabled in your settings ?
I've managed to update to remote-ssh extension v0.110.1, now connecting via SSH to a Ubuntu 18.04 host is working. Thanks.
The problem of connecting to WSL guest which runs Ubuntu 18.04 still exists.
WSL extension version: v0.88.0
Error message:
[2024-04-17 03:09:37.020] .vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by .vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node)
/cc @aeschli for the wsl extension
Have the same issues. Vscode version 1.88.1. Updated "Remote - SSH" extension to 0.110.1. Didn't help Dump from Output window:
[14:47:50.018] [server] /home/ednem/.vscode-server/cli/servers/Stable-e170252f762678dec6ca2cc69aba1570769a5d39/server/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/ednem/.vscode-server/cli/servers/Stable-e170252f762678dec6ca2cc69aba1570769a5d39/server/node)
Downgrading to 1.87.2 did help
I am seeing this issue on VSCode 1.88.1, portable installation, connecting to a RHEL 7.2 VM via the ssh-remote extension. This issue does not happen on VSCode 1.87.2. Remote - SSH extension version is v0.110.1. VSCode does not appear to recognize the need to use the legacy server and tries to run the one with GLIBC versions that are incompatible:
Server did not start successfully. Full server log at /login/radermb/.vscode-ser ver/.e170252f762678dec6ca2cc69aba1570769a5d39.log >>> /workspace/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node: /li b64/libm.so.6: version
GLIBC_2.27' not found (required by /workspace/.vscode-se rver/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node) /workspace/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node: /li b64/libc.so.6: version
GLIBC_2.25' not found (required by /workspace/.vscode-se rver/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node) /workspace/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node: /li b64/libc.so.6: versionGLIBC_2.28' not found (required by /workspace/.vscode-se rver/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node) /workspace/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node: /li b64/libstdc++.so.6: version
CXXABI_1.3.9' not found (required by /workspace/.vs code-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node) /workspace/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node: /li b64/libstdc++.so.6: versionGLIBCXX_3.4.20' not found (required by /workspace/. vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node) /workspace/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node: /li b64/libstdc++.so.6: version
GLIBCXX_3.4.21' not found (required by /workspace/. vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node)
I am experiencing this issue on Ubuntu 18.04.06 LTS running on a PC (AMD Ryzen 7 5700G with Radeon Graphics) attempting to install the Debian package recommended in the VS Code website where the Application leads you after checking for updates. All official references and procedures. No remote installation or access, all local to my PC.
Should I open a new bug report?
$ sudo dpkg -i code_1.88.1-1712771838_amd64.deb
Selecting previously unselected package code.
(Reading database ... 254481 files and directories currently installed.)
Preparing to unpack code_1.88.1-1712771838_amd64.deb ...
Unpacking code (1.88.1-1712771838) ...
dpkg: dependency problems prevent configuration of code:
code depends on libc6 (>= 2.28); however:
Version of libc6:amd64 on system is 2.27-3ubuntu1.6.
code depends on libgssapi-krb5-2 (>= 1.17); however:
Version of libgssapi-krb5-2:amd64 on system is 1.16-2ubuntu0.4.
code depends on libxkbfile1 (>= 1:1.1.0); however:
Version of libxkbfile1:amd64 on system is 1:1.0.9-2.
dpkg: error processing package code (--install):
dependency problems - leaving unconfigured
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for shared-mime-info (1.9-2) ...
Errors were encountered while processing:
code
see also #211718 - seems like this probably depends on mismatched extension versions, but was still frustrating to deal with!
On Ubuntu 18.04, I built the glibc-2.28 and install it to /opt/glibc-2.28, just like this post describes:
Reference: https://stackoverflow.com/a/77247394/2298014
When you do building, you should do it in a standalone "build" directory:
mkdir ~/src cd ~/src wget 'https://ftp.gnu.org/gnu/glibc/glibc-2.28.tar.gz' tar xzf glibc-2.28.tar.gz mkdir glibc-2.28-build cd glibc-2.28-build ../glibc-2.28/configure --prefix=/opt/glibc-2.28 make # make sure you can write to /opt/glibc-2.28 make install
Then after installing the package "patchelf":
# version "5c3e652f63e798a5ac2f31ffd0d863669328dc4c" is currently remote-ssh downloads and it depends on GLIBC_2.28 cd ~/.vscode-server/bin/5c3e652f63e798a5ac2f31ffd0d863669328dc4c cp node node_bak patchelf --set-interpreter /opt/glibc-2.28/lib/ld-linux-x86-64.so.2 --set-rpath /opt/glibc-2.28/lib:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu node # Now it runs: ./node v18.18.2
With this patch, v1.88 is working with my setup for now.
But this is obviously very cumbersome and fragile. Next time vscode server updates, you need to do patchelf for the new "node" binary.
And it is sad to know after Feb 2025, the systems with < GLIBC_2.28 will be unsupported.
Works for me.
VScode version: 1.89.1 Ubuntu version: 18.04
Hey @deepak1556 @connor4312, this issue might need further attention.
@zeroxia, you can help us out by closing this issue if the problem no longer exists, or adding more information.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
VSCode does show a popup window warning this:
But then it downloads this binary package:
~/.vscode-server/bin/5c3e652f63e798a5ac2f31ffd0d863669328dc4c
Testing it on command line:
Connecting to a WSL guest of Ubuntu 18.04, it downloads the same binary, so also failed with GLIBC_2.28 not found.
Downgrade to 1.87.2 both scenarios work without problem.
Remote-SSH logs with 1.88 (failed case):
Remote-SSH logs with 1.87.2 (successful case):