Remote: Iteration Plan for April 2020

[kieferrm]

This plan captures our work on the Remote development extensions in April. 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

Remote - SSH

Remote - Containers

• Finalize Dev Containers in WSL2 support (improve path mapping, discover devcontainer config files) Finalize Dev Containers in WSL2 support #2779 @chrmarti
• Improve the dev container configuration experience Improve the dev container configuration experience #2757 @egamma @chrmarti
• devcontainer.json add more variables like ${remoteWorkspaceFolder} Support ${remoteWorkspaceFolder} in devcontainer.json #2473 @chrmarti
• Explore support for Podman Podman support #116 @chrmarti
• 🏃 Explore speeding up container creation by caching extensions locally Docker: Extensions are always downloaded again #2227 @sandy081
• Adopt the latest devContainer.json improvements in the vscode-remote-try-* samples, e.g., forwardPorts. @Chuxel

Remote - WSL

• 🏃 Explore support for 'Save as Admin' Save as admin option. #1688 @aeschli

---

Deferred Items

• Polish Remote Explorer Header Remote Explorer: when there is only one view, split view should not be present vscode#86037 @alexr00 @misolori
• Can't drag files from a remote vscode window to a local window https://github.com/microsoft/vscode-remote-release/issues/1149 @isidorn
• Provide an easy way to access a SSH devbox through the web UI @roblourens
• Engineering - provide an integration test @aeschli

[BCNelson]

Is there a reason that #1688 is only under WSL? I would hope that it would be supported under all remotes.

[aeschli]

@BCNelson I will prototype it for WSL first, but it will then available for all remotes.

[PavelSosin-320]

I'm running Docker Desktop CE 2.3.0.0 edge on the top of Windows Pro dev pre-release of 2004 GA April 2000!. MS Dev containers running from Terminal window ignores my Docker context - see attachment text + son as logfile

DockerInfoJson.log

dockerInfo.txt
In other words, nothing ensures the correct execution of Microsoft development containers on my machine regardless of Microsoft's approval. This Docker stack will be most available ( no need in Hyper-V and DockerNAT ) and most performed (indeed!) very soon.
Please, pay attention to critical options like available networking options, init image, logging drivers, Swarm/Kubernetes orchestration mode. See attachment for the default, non-Kubernetes Docker infra configuration on my laptop.
DockerSwarm.txt

I don't believe that the ordinal developer is able to provide the correct values of docker run . The correct VSCode Docker plugin task has to be provided ASAP to avoid the user's inconvenience.