VSCode 1.88 remote connecting to Ubuntu 18.04 got "Missing GLIBC >= 2.28!" again #210033
Comments
|
If it can help: make sure you use the latest remote-ssh version ( |
|
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: |
|
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 installThen 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.2With 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. |
|
@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! |
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 ? |
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: |
|
/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 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:
|
|
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? |
|
see also #211718 - seems like this probably depends on mismatched extension versions, but was still frustrating to deal with! |
Works for me. VScode version: 1.89.1 |
|
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! |
vs-code-engineering
bot
closed this as not planned
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/5c3e652f63e798a5ac2f31ffd0d863669328dc4cTesting 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):
[17:27:34.945] Log Level: 2 [17:27:34.957] SSH Resolver called for "ssh-remote+os16u18", attempt 1 [17:27:34.957] "remote.SSH.useLocalServer": false [17:27:34.958] "remote.SSH.useExecServer": false [17:27:34.958] "remote.SSH.showLoginTerminal": false [17:27:34.958] "remote.SSH.remotePlatform": {"os16u18":"linux","z790":"linux"} [17:27:34.958] "remote.SSH.path": undefined [17:27:34.958] "remote.SSH.configFile": undefined [17:27:34.959] "remote.SSH.useFlock": true [17:27:34.959] "remote.SSH.lockfilesInTmp": false [17:27:34.959] "remote.SSH.localServerDownload": auto [17:27:34.959] "remote.SSH.remoteServerListenOnSocket": false [17:27:34.959] "remote.SSH.showLoginTerminal": false [17:27:34.959] "remote.SSH.defaultExtensions": [] [17:27:34.959] "remote.SSH.loglevel": 2 [17:27:34.959] "remote.SSH.enableDynamicForwarding": true [17:27:34.960] "remote.SSH.enableRemoteCommand": false [17:27:34.960] "remote.SSH.serverPickPortsFromRange": {} [17:27:34.960] "remote.SSH.serverInstallPath": {} [17:27:34.963] VS Code version: 1.88.0 [17:27:34.963] Remote-SSH version: [email protected] [17:27:34.963] win32 x64 [17:27:34.969] SSH Resolver called for host: os16u18 [17:27:34.969] Setting up SSH remote "os16u18" [17:27:34.977] Using commit id "5c3e652f63e798a5ac2f31ffd0d863669328dc4c" and quality "stable" for server [17:27:34.984] Install and start server if needed [17:27:34.993] Checking ssh with "C:\Windows\system32\ssh.exe -V" [17:27:34.997] Got error from ssh: spawn C:\Windows\system32\ssh.exe ENOENT [17:27:34.998] Checking ssh with "C:\Windows\ssh.exe -V" [17:27:35.000] Got error from ssh: spawn C:\Windows\ssh.exe ENOENT [17:27:35.000] Checking ssh with "C:\Windows\System32\Wbem\ssh.exe -V" [17:27:35.001] Got error from ssh: spawn C:\Windows\System32\Wbem\ssh.exe ENOENT [17:27:35.001] Checking ssh with "C:\Windows\System32\WindowsPowerShell\v1.0\ssh.exe -V" [17:27:35.002] Got error from ssh: spawn C:\Windows\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT [17:27:35.003] Checking ssh with "C:\Windows\System32\OpenSSH\ssh.exe -V" [17:27:35.132] > OpenSSH_for_Windows_8.1p1, Libre [17:27:35.133] > SSL 3.0.2[17:27:35.140] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 53279 os16u18 bash
[17:27:35.143] Terminal shell path: C:\Windows\System32\cmd.exe
[17:27:35.808] > �]0;C:\Windows\System32\cmd.exe�
[17:27:35.808] Got some output, clearing connection timeout
[17:27:36.540] > 4df7261f7066: running
[17:27:36.906] > Missing GLIBC >= 2.28!
[17:28:11.200] >
[17:28:11.212] Resolver error: Error: The VS Code Server failed to start
at g.ServerInstallError (c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:499668)
at d (c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:493011)
at t.handleInstallOutput (c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:495281)
at t.tryInstall (c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:620589)
at async c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:580447
at async t.withShowDetailsEvent (c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:583753)
at async k (c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:577412)
at async t.resolve (c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:581124)
at async c:\Users<HIDDEN_USERNAME>.vscode\extensions\ms-vscode-remote.remote-ssh-0.109.0\out\extension.js:2:847283
[17:28:11.216] ------
[17:28:13.135] "install" terminal command done
[17:28:13.136] Install terminal quit with output:
Remote-SSH logs with 1.87.2 (successful case):
[17:39:05.599] Log Level: 2 [17:39:05.608] SSH Resolver called for "ssh-remote+os16u18", attempt 1 [17:39:05.609] "remote.SSH.useLocalServer": false [17:39:05.609] "remote.SSH.useExecServer": false [17:39:05.609] "remote.SSH.showLoginTerminal": false [17:39:05.610] "remote.SSH.remotePlatform": {"os16u18":"linux","z790":"linux"} [17:39:05.610] "remote.SSH.path": undefined [17:39:05.610] "remote.SSH.configFile": undefined [17:39:05.610] "remote.SSH.useFlock": true [17:39:05.610] "remote.SSH.lockfilesInTmp": false [17:39:05.611] "remote.SSH.localServerDownload": auto [17:39:05.611] "remote.SSH.remoteServerListenOnSocket": false [17:39:05.611] "remote.SSH.showLoginTerminal": false [17:39:05.611] "remote.SSH.defaultExtensions": [] [17:39:05.611] "remote.SSH.loglevel": 2 [17:39:05.611] "remote.SSH.enableDynamicForwarding": true [17:39:05.611] "remote.SSH.enableRemoteCommand": false [17:39:05.612] "remote.SSH.serverPickPortsFromRange": {} [17:39:05.612] "remote.SSH.serverInstallPath": {} [17:39:05.615] VS Code version: 1.87.2 [17:39:05.616] Remote-SSH version: [email protected] [17:39:05.616] win32 x64 [17:39:05.624] SSH Resolver called for host: os16u18 [17:39:05.624] Setting up SSH remote "os16u18" [17:39:05.634] Using commit id "863d2581ecda6849923a2118d93a088b0745d9d6" and quality "stable" for server [17:39:05.640] Install and start server if needed [17:39:05.648] Checking ssh with "C:\Windows\system32\ssh.exe -V" [17:39:05.650] Got error from ssh: spawn C:\Windows\system32\ssh.exe ENOENT [17:39:05.650] Checking ssh with "C:\Windows\ssh.exe -V" [17:39:05.652] Got error from ssh: spawn C:\Windows\ssh.exe ENOENT [17:39:05.652] Checking ssh with "C:\Windows\System32\Wbem\ssh.exe -V" [17:39:05.654] Got error from ssh: spawn C:\Windows\System32\Wbem\ssh.exe ENOENT [17:39:05.654] Checking ssh with "C:\Windows\System32\WindowsPowerShell\v1.0\ssh.exe -V" [17:39:05.655] Got error from ssh: spawn C:\Windows\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT [17:39:05.655] Checking ssh with "C:\Windows\System32\OpenSSH\ssh.exe -V" [17:39:05.805] > OpenSSH_for_Windows_8.1p1, Lib [17:39:05.805] > reSSL 3.0.2[17:39:05.814] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 63822 os16u18 bash
[17:39:05.819] Terminal shell path: C:\Windows\System32\cmd.exe
[17:39:07.380] > �]0;C:\Windows\System32\cmd.exe�
[17:39:07.381] Got some output, clearing connection timeout
[17:39:08.035] > 217df585aa34: running
[17:39:08.163] > Missing GLIBC >= 2.28!
[17:39:12.201] >
[17:39:12.202] Remote server is listening on port 46009
[17:39:12.202] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":46009},"osReleaseId":"ubuntu","arch":"x86_64","webUiAccessToken":"","sshAuthSock":"","display":"","tmpDir":"/tmp","platform":"linux","connectionToken":"111aa111-a1a1-1a11-1a1a-a1111a11111a"},"downloadTime":1393,"installTime":2120,"serverStartTime":436,"installUnpackCode":"success"}
[17:39:12.212] Starting forwarding server. local port 63826 -> socksPort 63822 -> remotePort 46009
[17:39:12.215] Forwarding server listening on port 63826
[17:39:12.215] Waiting for ssh tunnel to be ready
[17:39:12.220] Tunneled port 46009 to local port 63826
[17:39:12.220] Resolved "ssh-remote+os16u18" to "port 63826"
[17:39:12.222] [Forwarding server port 63826] Got connection 0
[17:39:12.232] ------
[17:39:12.282] [Forwarding server port 63826] Got connection 1
[17:39:12.413] [Forwarding server port 63826] Got connection 2
[17:39:16.656] Opening exec server for ssh-remote+os16u18
[17:39:16.668] Initizing new exec server for ssh-remote+os16u18
[17:39:16.699] Using commit id "863d2581ecda6849923a2118d93a088b0745d9d6" and quality "stable" for server
[17:39:16.701] Install and start server if needed
[17:39:16.716] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 63835 os16u18 bash
[17:39:16.719] Terminal shell path: C:\Windows\System32\cmd.exe
[17:39:17.124] > �]0;C:\Windows\System32\cmd.exe�
[17:39:17.124] Got some output, clearing connection timeout
[17:39:17.499] > e59dd3b8e8d9: running
[17:39:18.834] Remote server is listening on port 35845
[17:39:18.834] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":35845},"osReleaseId":"ubuntu","arch":"x86_64","sshAuthSock":"","display":"","tmpDir":"/tmp","platform":"linux","execServerToken":"a1111111-a111-1aa1-a111-111a11aa1aa1"},"downloadTime":873,"installTime":347,"serverStartTime":82,"installUnpackCode":"success"}
[17:39:18.840] Starting forwarding server. local port 63842 -> socksPort 63835 -> remotePort 35845
[17:39:18.842] Forwarding server listening on port 63842
[17:39:18.842] Waiting for ssh tunnel to be ready
[17:39:18.845] Tunneled port 35845 to local port 63842
[17:39:18.845] Resolved "ssh-remote+os16u18" to "port 63842"
[17:39:18.845] Resolving exec server at port 63842
[17:39:18.848] [Forwarding server port 63842] Got connection 0
[17:39:18.853] [Forwarding server port 63842] Got connection 1
[17:39:18.857] >
[17:39:18.943] Exec server for ssh-remote+os16u18 created and cached
[17:39:18.966] Opening exec server for ssh-remote+os16u18
[17:39:18.987] Verified and reusing cached exec server for ssh-remote+os16u18
The text was updated successfully, but these errors were encountered: