Edits based on customer feedback #2630
Conversation
| @@ -195,14 +195,33 @@ SSH can be strict about file permissions and if they are set incorrectly, you ma | |||
|
|
|||
| ### Local SSH file and folder permissions | |||
|
|
|||
| #### macOS / Linux | |||
There was a problem hiding this comment.
H4s don't render very well on our site so I've been changing platform headers to bold text.
macOS / Linux:
I can update after the merge.
|
@gregvanl Sounds good! Good to know - will do that in future updates. |
|
Published |
| @@ -143,7 +143,9 @@ If you clone a Git repository using SSH and your SSH key has a passphrase, VS Co | |||
|
|
|||
| ### Docker Extension limitations | |||
|
|
|||
| 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`: | |||
| 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 in WSL or [inside a container](/docs/remote/containers.md) since the Docker CLI is not available by default in these environments. However, commands invoked from the Docker extension that rely on the Docker command line, for example **Docker: Show Logs**, fail. | |||
There was a problem hiding this comment.
Good job 👍 I'll admit I did not actually test wsl remote yet, but I do have an understanding of WSL and Docker, so I must point something out or ask something here. The text mentions that the Docker extension is running locally. It also points out it thus uses/works with the local Docker installation. As such, in both WSL and container, why would Docker: Show Logs not work? Both are local after all.
I understand why this is not the case when working over ssh, there it requires special consideration since dockerd and docker CLI is run remotely, whereas the Docker extension is local by default.
microsoft/vscode-remote-release#155
microsoft/vscode-remote-release#116
microsoft/vscode-remote-release#95
microsoft/vscode-remote-release#119