docs: update faq for linux client and remote (microsoft#6957)

* docs: add remote faq for older linux versions (microsoft#6953)

* docs: add remote faq for older linux versions

* Update docs/remote/faq.md

Co-authored-by: João Moreno <mail@joaomoreno.com>

* Update docs/remote/faq.md

Co-authored-by: João Moreno <mail@joaomoreno.com>

* Update docs/remote/faq.md

Co-authored-by: João Moreno <mail@joaomoreno.com>

* Update docs/remote/faq.md

Co-authored-by: João Moreno <mail@joaomoreno.com>

* Update docs/remote/faq.md

* Update docs/remote/faq.md

* Update docs/remote/faq.md

* Update docs/remote/faq.md

---------

Co-authored-by: João Moreno <mail@joaomoreno.com>
Co-authored-by: Nick Trogh <1908215+ntrogh@users.noreply.github.com>

* docs: add client faq for older linux versions (microsoft#6954)

* docs: add client faq for older linux versions

* Update docs/supporting/faq.md

* Update docs/supporting/faq.md

* Update docs/supporting/faq.md

---------

Co-authored-by: Nick Trogh <1908215+ntrogh@users.noreply.github.com>

---------

Co-authored-by: João Moreno <mail@joaomoreno.com>
Co-authored-by: Nick Trogh <1908215+ntrogh@users.noreply.github.com>

Author: 3 people

docs/remote/faq.md

@@ -101,12 +101,21 @@ You can use one of the following solutions to resolve this problem:
 
 ### What Linux packages or libraries need to be installed on a host to use Remote Development?
 
-Remote Development requires kernel >= 3.10, glibc >=2.17, and libstdc++ >= 3.4.18. Recent x86_64 glibc-based distributions have the best support, but exact requirements can vary by distribution.
+Remote Development requires kernel >= 4.18, glibc >=2.28, and libstdc++ >= 3.4.25. Recent x86_64 glibc-based distributions have the best support, but exact requirements can vary by distribution.
 
 Support for musl-based [Alpine Linux](https://alpinelinux.org) is available for the Dev Containers and WSL extensions and ARMv7l (AArch32) / ARMv8l (AArch64) is available in Remote - SSH. However, native dependencies in certain extensions may cause them not to function on non-x86_64 glibc distributions. Note that experimental ARMv8l (AArch64) is available in [VS Code Insiders](https://code.visualstudio.com/insiders/) only.
 
 See [Remote Development with Linux](/docs/remote/linux.md) for additional details.
 
+### Can I run VS Code Server on older Linux distributions?
+
+Starting with VS Code release 1.86, the minimum requirements for the build toolchain of the remote server were raised. The prebuilt servers distributed by VS Code are compatible with Linux distributions based on glibc 2.28 or later, for example, Debian 10, RHEL 8, Ubuntu 20.04.
+
+If your setup does not meet these requirements and you are unable to upgrade the Linux distribution, you can downgrade the VS Code client to version 1.85 to continue using Remote Development. You can downgrade the VS Code client on both desktop and web:
+
+* On desktop, you can download the VS Code release 1.85 from [here](https://code.visualstudio.com/updates/v1_85). Depending on your platform, make sure to disable updates to stay on that version. A good recommendation is to have release 1.85 as a separate installation, set up with [Portable Mode](https://code.visualstudio.com/docs/editor/portable). That way, you won't affect your main desktop VS Code version.
+* On web, you can add the following query argument [`?vscode-version=0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2`](https://vscode.dev/?vscode-version=0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2) to use VS Code release 1.85.
+
 ### Can I install individual extensions instead of the extension pack?
 
 Yes. The [Remote Development extension pack](https://aka.ms/vscode-remote/download/extension) provides a convenient way for you to access all of the latest remote capabilities as they are released. However, you can always install the individual extensions from the Marketplace or VS Code Extensions view.

docs/supporting/faq.md

@@ -299,6 +299,12 @@ VS Code desktop version starting with 1.83 (September 2023) is deprecating suppo
 
 VS Code will no longer provide product updates or security fixes on macOS Mojave (versions 10.14 and older) and VS Code version 1.85 will be the last available release for macOS Mojave (10.14 and older). You can learn more about upgrading your macOS version at [support.apple.com](https://support.apple.com/en-us/HT201260).
 
+## Can I run VS Code on older Linux distributions?
+
+Starting with VS Code release 1.86 (January 2024), VS Code desktop is only compatible with Linux distributions based on glibc 2.28 or later, for example, Debian 10, RHEL 8, or Ubuntu 20.04.
+
+If you are unable to upgrade your Linux distribution, the recommended alternative is to use our [web client](/docs/editor/vscode-web.md). If you would like to use the desktop version, then you can download the VS Code release 1.85 from [here](https://code.visualstudio.com/updates/v1_85). Depending on your platform, make sure to disable updates to stay on that version. A good recommendation is to set up the installation with [Portable Mode](/docs/editor/portable.md).
+
 ## Technical Support
 
 You can ask questions and search for answers on [Stack Overflow](https://stackoverflow.com/questions/tagged/vscode) and enter issues and feature requests directly in our [GitHub repository](https://github.com/microsoft/vscode/issues).

docs/supporting/requirements.md

@@ -23,8 +23,8 @@ VS Code is supported on the following platforms:
 
 * Windows 10 and 11 (64-bit)
 * macOS versions with Apple security update support. This is typically the latest release and the two previous versions.
-* Linux (Debian): Ubuntu Desktop 18.04, Debian 10
-* Linux (Red Hat): Red Hat Enterprise Linux 7, CentOS 7, Fedora 35
+* Linux (Debian): Ubuntu Desktop 20.04, Debian 10
+* Linux (Red Hat): Red Hat Enterprise Linux 8, Fedora 36
 
 ## Not supported
 
@@ -35,7 +35,7 @@ VS Code is supported on the following platforms:
 
 ### Additional Linux requirements
 
-* GLIBCXX version 3.4.21 or later
-* GLIBC version 2.17 or later
+* GLIBCXX version 3.4.25 or later
+* GLIBC version 2.28 or later
 
 For a list of currently known issues, see our [FAQ](faq).