[Remote-SSH Bug]: Error: Missing required dependencies #9485
Comments
|
Same problem here. I checked, I am able to open to do remote ssh in an ubuntu VM of aws ac2 but not inside that of a CENTOS VM. This is because, the centos VMs in aws have GLIBC==2.26 by default. Unfortunately after a lot of search I found out that there is no way to upgrade GLIBC to 2.31 (as it would cause lot of dependency conflicts). Unless the microsoft team helps with this, the only way around is to change the OS of the VM which will be harder than shifting to PyCharm. |
|
Same problem, Waiting for solution |
What you probably mean is that the system glibc cannot (easily) be upgraded. But it is possible to build anywhere you like a more recent version of glibc and to work around the problem. See #9467 |
|
Same problem here. |
|
I think I'm having the same problem. I’m able to download old versions of the code CLI using The code CLI makes using VSCode on compute clusters so easy, so I'm looking forward to a solution! |
|
Shifting back to 1.85.2 (VScode) and 0.108 of remote-ssh worked for me. |
Thank has worked also for me on mac. The issues started when I had to install version 1.86.0 of VS code |
|
Thanks! Downgrading also worked for me on mac. |
|
A short answer from my experience, downgrading to version 1.85.2 solves the issue. |
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServersettingConnect Locally
It connects successfully
->
No response
Expected Behavior
Until the last update it worked perfectly and there were no dependency errors. Now, even installing the previous version it still does not work.
In the vscode-server .log file it says
Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.19
Warning: Missing GLIBC >= 2.28! from /usr/lib64/libc-2.17.so
Error: Missing required dependencies. Please refer to our FAQ https://aka.ms/vsc
ode-remote/faq/old-linux for additional information.
Steps To Reproduce
No response
Remote-SSH Log
Remote-SSH Log
Anything else?
No response
The text was updated successfully, but these errors were encountered: