Remote Development FAQ
AI agents: See llms.txt for documentation discovery and navigation. Documentation articles are also available as Markdown by appending .md to the article URL. Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Remote Development FAQ View as Markdown Ask in VS Code Ask in VS Code Insiders This article covers frequently asked questions for each of the Visual Studio Code Remote Development extensions.
See the SSH , Containers , and WSL articles for more details on setting up and working with each of their respective capabilities. Or try the introductory Tutorials to help get you running quickly in a remote environment. For questions about GitHub Codespaces , see the GitHub Codespaces documentation . General What is Visual Studio Code Remote Development? The Visual Studio Code Remote Development extension pack allows you to open any folder in a container, on a remote machine (via SSH), or in the Windows Subsystem for Linux and take advantage of VS Code's full feature set.
This means that VS Code can provide a local-quality development experience — including full IntelliSense (completions), debugging, and more — regardless of where your code is located or hosted. What advantages does VS Code Remote Development provide over local editing? Some benefits of remote development include: Being able to edit, build, or debug on a different OS than you are running locally. Being able to develop in an environment that matches the target deployment environment.
Using larger or more specialized hardware than your local machine for development. The ability to edit code stored in another location, such as in the cloud or at a customer site. Separating developer environments to avoid conflicts, improve security, and speed up on-boarding. Compared to using a network share or synchronizing files, VS Code Remote Development provides dramatically better performance along with better control over your development environment and tools.
How do the Remote Development extensions relate to GitHub Codespaces? GitHub Codespaces is a service that provides managed cloud-hosted development environments accessible from both VS Code and a new browser-based editor. The service also allows VS Code and the browser-based editor to access self-hosted environments (desktop or server) without requiring an SSH server or even a direct network route. You can read more in the GitHub Codespaces documentation .
While the Remote Development and Codespaces extensions share technology and features, the Remote Development extensions are released separately and can operate independently from GitHub Codespaces. How do the Remote Development extensions work? Visual Studio Code Remote Development allows your local VS Code installation to transparently interact with source code and runtime environments on other machines (whether virtual or physical) by moving the execution of certain commands to a "remote server".
The VS Code Server is quickly installed by VS Code when you connect to a remote endpoint and can host extensions that interact directly with the remote workspace, machine, and file system. See Supporting Remote Development for additional details about extensions. How do the Remote Development extensions secure access to a remote machine, VM, or container? Visual Studio Code Remote Development uses existing, well known transports like secure shell to authenticate and secure traffic.
No ports need to be publicly opened beyond those used by these well-known, secure transports. The VS Code Server that is injected runs as the same user you used to sign in to the machine, ensuring that VS Code and its extensions are not given improper elevated access without permission. The server is started and stopped by VS Code and is not wired into any user or global login or startup scripts. VS Code manages the server's lifecycle so you do not need to worry about whether or not it is running.
Can VS Code Server be installed or used on its own? No. The VS Code Server is a component of the Remote Development extensions and is managed by a VS Code client. It is installed and updated automatically by VS Code when it connects to an endpoint and if installed separately could become quickly out of date. It is not intended or licensed for use by other clients. What are the connectivity requirements for VS Code Server?
Installation of VS Code Server requires that your local machine have outbound HTTPS (port 443) connectivity to: update.code.visualstudio.com vscode.download.prss.microsoft.com By default, the Remote - SSH will attempt to download on the remote host, and fail back to downloading VS Code Server locally and transferring it remotely once a connection is established. You can change this behavior with the remote.SSH.localServerDownload Open in VS Code Open in VS Code Insiders setting to always download locally and then transfer it, or to never download locally.
The Dev Containers extension always downloads locally and transfers into the container. You can install extensions manually without an internet connection using the Extensions: Install from VSIX... command, but if you use the extension panel or devcontainer.json to install extensions, your local machine and VS Code Server will need outbound HTTPS (port 443) access to: marketplace.visualstudio.com *.gallerycdn.vsassets.io (Azure CDN) Finally, some extensions (like C#) download secondary dependencies from download.microsoft.com or download.visualstudio.microsoft.com .
Others (like Visual Studio Live Share ) may have additional connectivity requirements. Consult the extension's documentation for details if you run into trouble. All other communication between the server and the VS Code client is accomplished through the following transport channels depending on the extension: SSH: An authenticated, secure SSH tunnel. Containers: Docker's configured communication channel (via docker exec ).
WSL: A random local port. You can find a list of locations VS Code itself needs access to in the network connections article . Why can't I see my local containers in the Container Tools extension when using the Remote - extensions? By default, the Container Tools extension will run remotely. While this is a sensible default in some cases, it means the extension may not show local containers when VS Code is connected to a remote SSH host, container, or WSL.
You can use one of the following solutions to resolve this problem: Open a new local window ( File > New Window ) and use it to work with local containers. Install the Dev Containers extension and use the Remote Explorer in situations when you need to see your local containers. WSL only : Use the Docker Technical Preview for WSL 2 or configure Docker Desktop for use in WSL 1 . Dev Containers only : Forward the Docker socket and install the Docker CLI (only) in the container.
Use the extensionKind property to force the extension to be ui . However, this will prevent some commands from working. What Linux packages or libraries need to be installed on a host to use Remote Development? 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 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 only. See Remote Development with Linux for additional details. Can I run VS Code Server on older Linux distributions? Starting with VS Code release 1.99 (March 2025), the prebuilt servers distributed by VS Code are only compatible with Linux distributions that are based on glibc 2.28 or later.
These include for example, Debian 10, RHEL 8, or
The rest of this page is on the live site.