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
Why does this extension need docker for windows on windows to work? It should only need a docker client, DOCKER_HOST and DOCKER_CERT_PATH environment, right? Or is it already possible to work with a minikube/WSL environment?
The text was updated successfully, but these errors were encountered:
Chuxel
transferred this issue from microsoft/vscode-dev-containers
Jul 27, 2019
@remoe The extension uses the Docker CLto wire up and communicate with the container. To make things easy when you just want to open a local folder in a container, we also "bind" mount the local filesystem by default. Docker doesn't allow binding remote filesystems (which would result in really poor performance if they did). However, you can tweak devcontainer.json or your Docker Compose file to work with remote hosts. Technically the Docker daemon / service does not need to be local - just the latest version of the CLI for docker and docker-compose (if you use it).
Why does this extension need docker for windows on windows to work? It should only need a docker client, DOCKER_HOST and DOCKER_CERT_PATH environment, right? Or is it already possible to work with a minikube/WSL environment?
The text was updated successfully, but these errors were encountered: