Remote Development with Linux
Linux is a highly variable environment and the large number of server, container, and desktop distributions can make it difficult to know what is supported. Visual Studio Code Remote Development has prerequisites for the specific host / container / WSL distribution you will be connecting to.
If you are using a recent stable/LTS version of:
- Ubuntu 64-bit x86 (16.04+)
- Debian 64-bit x86 (8+)
- CentOS / RHEL 64-bit x86 (7+)
then the VS Code Remote Development extensions should work without additional dependencies.
VS Code Insiders also has experimental support for:
- Raspbian 32-bit ARMv7l (or ARMv8 in 32-bit mode) (Stretch/9+) SSH hosts (Remote - SSH). ARMv6 used in the Raspberry Pi 1/Zero is not supported.
- Alpine Linux 64-bit x86 (3.7+) containers (Remote - Containers) and WSL hosts (Remote - WSL)
However, if you are using a non-standard configuration or downstream distribution, you may run into issues. This document provides information on requirements as well as tips to help you get up and running even if your configuration is only community-supported.
Note that other extensions may have dependencies beyond those listed here. Some extensions also contain compiled native code that may not work on Alpine Linux or ARMv7l. If you encounter an issue that only occurs with a particular extension, contact the extension authors for information on their native dependencies.
Local Linux prerequisites
If you are running Linux locally, the VS Code prerequisites drive most of the requirements.
In addition, specific Remote Development extensions have further requirements:
- Remote - SSH:
sshneeds to be in the path. The shell binary is typically in the
- Remote - Containers: Docker CE/EE 18.06+ and Docker Compose 1.21+. Follow the official install instructions for Docker CE/EE for your distribution. If you are using Docker Compose, follow the Install Docker Compose directions as well. (Note that the Ubuntu Snap package is not supported and packages in distributions may be out of date.)
docker-composemust also be in the path. However, Docker does not need to be running if you are using a remote host.
Remote host / container / WSL Linux prerequisites
You may encounter issues with certain extensions with native dependencies when using VS Code Insiders with 32-bit ARMv7l glibc-based Linux SSH hosts and 64-bit x86 musl-based Alpine Linux containers. For ARMv7l in VS Code Insiders, extensions may only include x86_64 versions of native modules or runtimes in the extension. For Alpine Linux in VS Code Insiders, included native code or runtimes may not work due to fundamental differences between how
libc is implemented in Alpine Linux (
musl) and other distributions (
glibc). In both these cases, extensions will need to opt-in to supporting these platforms by compiling / including binaries for these additional targets. Please raise an issue with the appropriate extension author requesting support if you encounter an extension that does note work as expected.
|Distribution||Base Requirements||Remote - SSH Requirements||Notes|
|General||kernel >= 3.10, glibc >=2.17, libstdc++ >= 3.4.18, Python 2.6 or 2.7, tar||OpenSSH server,
|Ubuntu 16.04+, Debian 8+, Raspbian Stretch/9+ and downstream distributions||
||Requires kernel >= 3.10, glibc >= 2.17, libstdc++ >= 3.4.18. Debian < 8 (Jessie) and Ubuntu < 14.04 do not meet this requirement.|
|RHEL / CentOS 7+||
||Requires kernel >= 3.10, glibc >= 2.17, libstdc++ >= 3.4.18. RHEL / CentOS < 7 does not meet this requirement without using a workaround to upgrade.|
|🔬 Alpine Linux 3.7+||
||Not yet supported.||Supported in Remote - Containers and Remote - WSL. Extensions installed in the container may not work due to
Tips by Linux distribution
The following is a list of distributions and any base requirements that may be missing. End-of-life versions of distributions are not included.
|Server Distribution||Docker Image||Missing libraries||Notes / additional steps|
|🔬 Alpine Linux 3.10 (64-bit)||
||Supported in Remote - Containers and Remote - WSL only. Extensions installed in the container may not work due to
|✅ CentOS 7 Server (64-bit)||
|⚠️ CentOS 6 Server (64-bit)||
||Requires a workaround.|
|✅ Debian 9 Server (64-bit)||
|✅ Debian 8 Server (64-bit)||
|✅ openSUSE Leap Server 15 (64-bit)||
||Docker image is missing
|✅ openSUSE Leap Server 42.3 (64-bit)||
||Docker image is missing
|✅ Oracle Linux 7 (64-bit)||
|⚠️ Oracle Linux 6 (64-bit)||
||Requires a workaround.|
|🔬 Raspbian Stretch/9 (ARMv7l 32-bit)||<none>||Supported in Remote - SSH. Extensions may not work when installed on an ARMv7l host due to extension x86 native code.|
|✅ RedHat Enterprise Linux 7 (64-bit)||<none>||<none>|
|⚠️ RedHat Enterprise Linux 6 (64-bit)||
||Requires a workaround.|
|✅ SUSE Linux Enterprise Server 15 (64-bit)||<none>||<none>|
|✅ SUSE Linux Enterprise Server 12 (64-bit)||<none>||<none>|
|❌ SUSE Linux Enterprise Server 11 (64-bit)||
||Might work compiling glibc from source, but untested.|
|✅ Ubuntu Server 19.04 (64-bit)||
|✅ Ubuntu Server 18.04 (64-bit)||
|✅ Ubuntu Server 16.04 (64-bit)||
|✅ Ubuntu Server 14.04 (64-bit)||
Updating glibc and libstdc++ on RHEL / CentOS 6
RHEL / CentOS 6 ships with glibc 2.12 and libstdc++ 3.4.13. Unfortunately, this does not meet the requirements for Remote Development. RHEL / CentOS 6 goes out of support in 2020, so we strongly recommend upgrading to RHEL / CentOS 7 or higher.
However, as a workaround, you can either build glibc manually or use the following script to install updated binaries. The bash script below will upgrade these libraries without having to build them. It is adapted from information in this article, this gist, and this Fedora copr project. The article also includes instructions for manually building glibc if you would prefer not to use the binaries from the article.
Do not run this script on anything mission critical without a rollback strategy since it does update libraries that other applications depend on.
For servers, run the following script and restart the server so the updates take effect.
# Update glibc and static libs wget http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-2.17-55.el6.x86_64.rpm wget http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-common-2.17-55.el6.x86_64.rpm wget http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-devel-2.17-55.el6.x86_64.rpm wget http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-headers-2.17-55.el6.x86_64.rpm wget https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-utils-2.17-55.el6.x86_64.rpm wget https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-static-2.17-55.el6.x86_64.rpm sudo rpm -Uh --force --nodeps \ glibc-2.17-55.el6.x86_64.rpm \ glibc-common-2.17-55.el6.x86_64.rpm \ glibc-devel-2.17-55.el6.x86_64.rpm \ glibc-headers-2.17-55.el6.x86_64.rpm \ glibc-static-2.17-55.el6.x86_64.rpm \ glibc-utils-2.17-55.el6.x86_64.rpm # Update libstdc++ wget https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/gcc-4.8.2-16.3.fc20/libstdc++-4.8.2-16.3.el6.x86_64.rpm wget https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/gcc-4.8.2-16.3.fc20/libstdc++-devel-4.8.2-16.3.el6.x86_64.rpm wget https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/gcc-4.8.2-16.3.fc20/libstdc++-static-4.8.2-16.3.el6.x86_64.rpm sudo rpm -Uh \ libstdc++-4.8.2-16.3.el6.x86_64.rpm \ libstdc++-devel-4.8.2-16.3.el6.x86_64.rpm \ libstdc++-static-4.8.2-16.3.el6.x86_64.rpm
In a container environment, you can add similar contents to a Dockerfile:
FROM centos:6 RUN yum -y install wget tar # Update glibc RUN wget -q http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-2.17-55.el6.x86_64.rpm \ && wget -q http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-common-2.17-55.el6.x86_64.rpm \ && wget -q http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-devel-2.17-55.el6.x86_64.rpm \ && wget -q http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-headers-2.17-55.el6.x86_64.rpm \ && wget -q https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-utils-2.17-55.el6.x86_64.rpm \ && wget -q https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-static-2.17-55.el6.x86_64.rpm \ && rpm -Uh --force --nodeps \ glibc-2.17-55.el6.x86_64.rpm \ glibc-common-2.17-55.el6.x86_64.rpm \ glibc-devel-2.17-55.el6.x86_64.rpm \ glibc-headers-2.17-55.el6.x86_64.rpm \ glibc-static-2.17-55.el6.x86_64.rpm \ glibc-utils-2.17-55.el6.x86_64.rpm \ && rm *.rpm # Update libstdc++ RUN wget -q https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/gcc-4.8.2-16.3.fc20/libstdc++-4.8.2-16.3.el6.x86_64.rpm \ && wget -q https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/gcc-4.8.2-16.3.fc20/libstdc++-devel-4.8.2-16.3.el6.x86_64.rpm \ && wget -q https://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/gcc-4.8.2-16.3.fc20/libstdc++-static-4.8.2-16.3.el6.x86_64.rpm \ && rpm -Uh \ libstdc++-4.8.2-16.3.el6.x86_64.rpm \ libstdc++-devel-4.8.2-16.3.el6.x86_64.rpm \ libstdc++-static-4.8.2-16.3.el6.x86_64.rpm \ && rm *.rpm # Set the default shell to bash instead of sh ENV SHELL /bin/bash