You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Originally posted by @PavelSosin-320 in #2752 (comment)
The text was updated successfully, but these errors were encountered: