-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Dev Containers]the local WSL starts automatically when connecting to a container on a REMOTE host #9905
Comments
Yes, thank you so much, the issue is resolved. I'm sorry for taking up your time. With this, I can use WSL services within the container, like ssh-agent, even if it's a remote container, right? I‘d seen #9897 . I think, just for me, this should not be enabled by default. Perhaps a notification or prompt would be helpful? |
Correct. You still get the ssh-agent forwarded from Windows (if it is running) when you disable this setting.
We are trying to avoid adding more noise to the UI. I assume most users are fine with the default WSL distro starting and this user setting can be used to avoid it when needed. Thanks. |
I have very little memory on this host, so I'm working on a remote host. I often find that WSL starts up automatically.
Until I found this in the Dev Containers logs
I'm connecting to a container on a remote host, why do I need to turn on the local WSL?
The logs of the port forwarding made me think it had to be forwarded to WSL.
After 'wsl --shutdown'
But the remote connection and port forwarding were not interrupted.
So turning on the local WSL doesn't do anything.
The text was updated successfully, but these errors were encountered: