Remote: Iteration Plan for November 2019

[kieferrm]

This plan captures our work on the Remote development extensions in November. We follow the same iteration cycle as VS Code. Although we plan for a whole iteration, we not only ship at the end of an iteration but throughout.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team

Remote - Core

• Revisit the Remote Explorer layout to better support different remote types Implement new UI for remote explorer (and reconcile with forwarded ports UI) #1778 @alexr00
• 🏃 Provide common UI for port forwarding Unified port forwarding UI #1777 @alexr00

Remote - SSH

None.

Remote - Containers

• Improve provisioning and startup performance of a dev container Improve provisioning and startup performance of a dev container #1823 @chrmarti
• Investigate support to install extensions into a named volume Add option to use volume to avoid reinstalling extensions, VS Code Server on container rebuild #421 @chrmarti
• Investigate: Reducing reliance on runArgs for common scenarios: mount points, environment variables Investigate: Reducing reliance on runArgs for common scenarios: mount points, environment variables #1201 @chrmarti
• Investigate supporting user/group id as configuration option Dynamically source the UID and GID when starting devcontainer on Linux #1155 @chrmarti
• Support settings property in attached config files Support settings property in attached config files #1589 @chrmarti
• Permit use of Remote Container using SSH transport Permit use of Remote Container using SSH transport #636 @chrmarti
• Investigate pre-building a subset of vscode-dev-containers to speed up first time experiences Pre-build images for Microsoft maintained container images in this repository vscode-dev-containers#140 @Chuxel - Investigation done, next is completing implementation.
• Open repository in container - support more than one container for a repository Allow more than one repository container to exist #1581 @egamma
• Include guidance for how to use Remote Containers as a sandbox for multiple projects/folders (new quick start) @Chuxel
• Container Blog post series @bowdenk7 @gregvanl

Remote - WSL

• 🏃 WSL2 + Docker Blog post @fiveisprime @gregvanl
• Add VS Code + Remote WSL extension in Windows/WSL 2 docs @fiveisprime

---

Deferred Items

• 🏃 Open repository in container - support private repositories (private repos, more flexible volume usage) Open Repository in Container does not work with private repos (even if credential manager setup) #1578 @egamma @chrmarti
• Adopt common port forwarding UI in Remote-SSH @roblourens
• Adopt common port forwarding UI in Remote-Containers @chrmarti

[bhack]

Please add some kind of initial Kubernetes support #12.
Community cannot contribute to this close source plugin. So please evaliate that as the top feature requested with the container label (other than podman).

[Dijir]

It would be interesting to have the Remote - Containers extension available for Remote WSL.
Thus the extension would make use of the wsl2 virtual machine docker itself, greatly improving the processing speed of the files that already are on the vm.

[chrmarti]

@Dijir Remote-Containers should already show the WSL2 containers. Could you open an issue if that doesn't work?