Skip to content

Commit 863a1a4

Browse files
committed
https://github.com/Microsoft/vscode-remote-release/issues/11
1 parent febccbe commit 863a1a4

File tree

3 files changed

+3
-0
lines changed

3 files changed

+3
-0
lines changed

docs/remote/containers.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -599,6 +599,7 @@ See the following examples dev containers for additional information:
599599
* Alpine Linux or Windows container images are not yet supported. Most images come with a Debian or Ubuntu based flavor you can use instead. (Typically Alpine variations end in `-alpine`).
600600
* All roots/folders in a multi-root workspace will be opened in the same container, regardless of whether there are configuration files at lower levels.
601601
* The unofficial Ubuntu Docker **snap** package for Linux is **not** supported. Follow the [official Docker install instructions for your distribution](https://docs.docker.com/install/#supported-platforms).
602+
* When installing an extension pack in a container, extensions may install locally instead of inside the container. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. See [vscode-remote-release #11](https://github.com/Microsoft/vscode-remote-release/issues/11) for details.
602603
* If you clone a Git repository using SSH and your SSH key has a passphrase, VS Code's pull and sync features may hang when running remotely. Either use a SSH key without a passphrase, clone using HTTPS, or run `git push` from the command line to work around the issue.
603604
* Local proxy settings are not reused inside the container, which can prevent extensions from working unless the appropriate proxy information is configured (for example global `HTTP_PROXY` or `HTTPS_PROXY` environment variables with the appropriate proxy information).
604605

docs/remote/ssh.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -169,6 +169,7 @@ VS Code's local user settings are also reused when you are connected to an SSH h
169169
- Linux hosts must have Bash (`/bin/bash`), `tar`, and either `curl` or `wget` installed.
170170
- PuTTY is not supported on Windows.
171171
- You cannot drag files out of the File Explorer to your local filesystem to copy them.
172+
- When installing an extension pack when connected to a SSH host, extensions may install locally instead of inside on the host. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. See [vscode-remote-release #11](https://github.com/Microsoft/vscode-remote-release/issues/11) for details.
172173
- If you clone a Git repository using SSH and your SSH key has a passphrase, VS Code's pull and sync features may hang when running remotely. Either use a SSH key without a passphrase, clone using HTTPS, or run `git push` from the command line to work around the issue.
173174
- Local proxy settings are not reused on the remote host, which can prevent extensions from working unless the appropriate proxy information is configured on the remote host (for example global `HTTP_PROXY` or `HTTPS_PROXY` environment variables with the appropriate proxy information).
174175
- See [here for a list of active issues](https://aka.ms/vscode-remote/ssh/issues) related to SSH.

docs/remote/wsl.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -115,6 +115,7 @@ See [here for a list of active issues](https://aka.ms/vscode-remote/wsl/issues)
115115
| Issue | Existing issues |
116116
|---|---|
117117
Non-empty folders in the open workspace can't be renamed | https://github.com/Microsoft/WSL/issues/3395, https://github.com/Microsoft/WSL/issues/1956
118+
| When installing an extension pack in WSL, extensions may install locally instead of in WSL. Click the **Install** button for each extension in the Local section of the extension panel to work around the issue. | [vscode-remote-release #11](https://github.com/Microsoft/vscode-remote-release/issues/11) |
118119

119120
In addition, local proxy settings are not reused by VS Code running in WSL, which can prevent extensions from working without adding a global `HTTP_PROXY` and `HTTPS_PROXY` environment variable with the appropriate proxy information.
120121

0 commit comments

Comments
 (0)