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.
Below is a summary of the top level plan items.
Legend of annotations:
| Mark | Description |
| ------------------- | ------------------------------------------------- |
| :runner: | work in progress |
| :hand: | blocked task |
| :muscle: | stretch goal for this iteration |
| :red_circle: | missing issue reference |
| :large_blue_circle: | more investigation required to remove uncertainty |
| :black_circle: | under discussion within the team |
devcontainer.json add more variables like ${remoteWorkspaceFolder} https://github.com/microsoft/vscode-remote-release/issues/2473 @chrmartidevContainer.json improvements in the vscode-remote-try-* samples, e.g., forwardPorts. @ChuxelIs there a reason that #1688 is only under WSL? I would hope that it would be supported under all remotes.
@BCNelson I will prototype it for WSL first, but it will then available for all remotes.
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
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.
Most helpful comment
@BCNelson I will prototype it for WSL first, but it will then available for all remotes.