[kaelinl]

This messed with me too. At work our primary development environment is a farm of older CentOS machines. They all lost support with this vscode upgrade. It probably impacts hundreds of people. I had to send out instructions to downgrade and pin your vscode version while we look for a workaround.

I get that it isn't entirely within the vscode team's control (Electron chose to make the switch), but even then, it really interferes with a lot of people's daily development needs. These systems aren't particularly old or out of support.

[funkychicken]

I just helped a coworker get his remote vscode working on RHEL7. If you compile glibc from source and install it in some local directory, you can run patchelf —set-interpreter —set-path on ~/.vscode-server/bin/*/node and write to a special “skip requirements file”

touch /tmp/vscode-skip-server-requirements-check

patchelf --set-interpreter /opt/glibc/lib/ld-linux-x86-64.so.2 --set-rpath /opt/glibc/lib:/opt/glibc/lib64 ~/.vscode-server/bin/*/node Warning: you’ll need gmake and all the gnu tools for building, make sure to ../configure with —disable-werror

[dmm]

> while we look for a workaround.

emacs will always be there for you, when you're ready.

[Twirrim]

> These systems aren't particularly old or out of support.

CentOS 7 goes EOL June 30th, so you're pretty close to their end of life (CentOS 8 stream has 2.28, so should still work with the new vscode version, which is why I'm guessing you're talking about 7.)

If you don't already have plans for replacement/upgrading, you really need to have plans.

[mikeravkine]

Ubuntu 18 went EOL on May 31, 2023 so about 8 months ago. What CentOS are you running that's still in support and was affected by this change? I had to upgrade all my systems last year after the EOL as most python packages dropped 3.8 support.

[bitfilped]

CentOS 7 with the EOL of June 30, 2024 was affected.