VSCode stopped supporting an old glibc version and near EOL users are in trouble

thesuperbigfrog · 2024-02-02T12:42:52

Summary of the issue:

There will be a significant number of Linux machines that will be unable to Visual Studio Code (VS Code) v1.86 (the latest version).

This is due to VS Code v1.86 requiring glibc >= 2.28.

Impacted Linux distros include Ubuntu 18.04, RHEL7 / CentOS 7, Amazon Linux 2, and more.

Impacted users include many researchers in medicine / government / academia, scientific equipment, Amazon EC2 customers, and others.

Some potential workarounds posted in the GitHub thread, but no definitive support path for those who are unable to upgrade at this time.

TheLoafOfBread · 2024-02-02T17:36:52

> Amazon EC2 customers

They can easily start an instance with fresher version of Linux or startup Windows. Anyway who really develops on an EC2 instance? That sounds very expensive to get such instance which is actually able to run VScode in some sane speed.

smackeyacky · 2024-02-02T12:57:57

Half the time I end up dropping to a cli anyway. At this point I’m really not sure what VSCode adds once you’ve learned the tool at hand. Node or .Net or whatever can all be programmed effectively outside of VSCode. Just ditch it.

xinayder · 2024-02-02T13:15:48

What IDE do you use? nvim? emacs?

smackeyacky · 2024-02-02T16:34:57

Vim. It’s enough for a lot of tasks in common languages

altairprime · 2024-02-02T16:42:57

The issue has been locked to prevent further comment. The latest reply as of now is:

> We'll be following up with next steps for a viable alternative workaround in #203375, that does not involve disabling updates.

nunez · 2024-02-02T15:05:50

i guess this is a +1 for vim and emacs!

nullpilot · 2024-02-02T13:43:36

The latest versions of Node, Bun and Godot stopped working recently as well.