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
Despite the documentation explains several ways of working with remote docker hosts for the Remote - Containers extension, none of them is optimal, since it requires additional configuration on at least one of:
VSCode settings (docker.host)
The host environment (install docker cli, or configure the env using docker-machine)
The devcontainer (because of bind mounts, and because SSHFS is not fast enough)
It would be much simpler if the Remote - Containers extension could integrate with Remote - SSH, so it could spawn new devcontainers using the existing tools (docker cli) found in the Remote - SSH current session.
This would be similar to how Remote - WSL and Remote - Containers interoperates.
So, users within a Remote - SSH session could see an option Reopen in Container in the remote options for that session.
The text was updated successfully, but these errors were encountered:
Despite the documentation explains several ways of working with remote docker hosts for the Remote - Containers extension, none of them is optimal, since it requires additional configuration on at least one of:
docker.host
)It would be much simpler if the Remote - Containers extension could integrate with Remote - SSH, so it could spawn new
devcontainer
s using the existing tools (docker cli) found in the Remote - SSH current session.This would be similar to how Remote - WSL and Remote - Containers interoperates.
So, users within a Remote - SSH session could see an option Reopen in Container in the remote options for that session.
The text was updated successfully, but these errors were encountered: