Skip to content

Commit 25fca59

Browse files
author
Greg Van Liew
committed
2 parents f8be520 + 74f414e commit 25fca59

File tree

5 files changed

+22
-2
lines changed

5 files changed

+22
-2
lines changed

docs/remote/faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,9 +59,9 @@ The VS Code Server requires outbound HTTPS (port 443) connectivity to `update.co
5959

6060
Most Linux distributions will not require additional dependency installation steps. For SSH, Linux hosts need to have Bash (`/bin/bash`), `tar`, and either `curl` or `wget` installed which could be missing from certain stripped down distributions. However, [Alpine Linux](https://alpinelinux.org) is currently not supported.
6161

62-
### Can the Docker Extension run as a Workspace Extension in a remote setup?
62+
### Can the Docker extension run as a remote "workspace" extension?
6363

64-
The Docker extension is by default configured as a UI extension. This enables the extension to work better with a Docker machine that runs locally while you are developing inside a container. If you want to run the Docker Extension on the workspace side, so that it communicates with a remotely installed Docker machine, then you can configure the Docker extension to run remotely using the following user setting:
64+
The Docker extension is configured to run as a local "UI" extension by default. This enables the extension to work with your local Docker installation when you are developing inside a container. However, you may want to use the extension with a Docker Machine installed on a remote host instead. Fortunately, you can configure the Docker extension to run on the host by adding the following to `settings.json`:
6565

6666
```json
6767
"remote.extensionKind": {
12.2 KB
Loading
13.4 KB
Loading

docs/remote/ssh.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -172,6 +172,16 @@ VS Code's local user settings are also reused when you are connected to an SSH h
172172
- 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).
173173
- See [here for a list of active issues](https://aka.ms/vscode-remote/ssh/issues) related to SSH.
174174

175+
### Docker Extension limitations
176+
177+
The Docker extension is configured to run as a local "UI" extension by default. This enables the extension to work with your local Docker installation when you are developing inside a container. However, you may want to use the extension with a Docker Machine installed on a remote host instead. Fortunately, you can configure the Docker extension to run on the host by adding the following to `settings.json`:
178+
179+
```json
180+
"remote.extensionKind": {
181+
"peterjausovec.vscode-docker": "workspace"
182+
}
183+
```
184+
175185
### Extension limitations
176186

177187
Many extensions will work on remote SSH hosts modification. However, in some cases, certain features may require changes. If you run into an extension issue, there is [a summary of common problems and solutions](/docs/remote/troubleshooting.md#extensiont-tips) that you can mention to the extension author when reporting the issue.

docs/remote/wsl.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,16 @@ NodeJS Error: spawn EACCES (different variants of this error) | https://github.c
131131
Webpack HMR not working | https://github.com/Microsoft/WSL/issues/2709 |
132132
Firebase via node unusably slow only on WSL | https://github.com/Microsoft/WSL/issues/2657 |
133133

134+
### Docker Extension limitations
135+
136+
The Docker extension is configured to run as a local "UI" extension that runs on the Windows side by default. This enables the extension to work with your local Docker installation when you are developing inside a container. However, some Docker commands invoked from the Docker extension can fail from a WSL window. If you want the Docker extension to interact with an installed Docker CLI in WSL instead, add the following to `settings.json`:
137+
138+
```json
139+
"remote.extensionKind": {
140+
"peterjausovec.vscode-docker": "workspace"
141+
}
142+
```
143+
134144
### Extension limitations
135145

136146
Many extensions will work in WSL without modification. However, in some cases, certain features may require changes. If you run into an extension issue, [see here for a summary of common problems and solutions](/docs/remote/troubleshooting.md#extensiont-tips) that you can mention to the extension author when reporting the issue.

0 commit comments

Comments
 (0)