vscode-remote-release
vscode-remote-release copied to clipboard
remote-container does not work
I can connect the remote service by remote-ssh, but the remote-container dose not work.
could you help me?
when i click on the button "Attach to running container", remote-containers show log
Does ssh 10.44.171.206 /bin/sh
work when you run it from the command line? Does it require any keyboard input?
No, it dose not work. It require keyboard input, just like the following.
Hi, I'm having the same issues since the last Win11 22H2 update. I'm working in a Windows 11 PC connected through ssh to a Linux 22.04 LTS machine. In this machine, Docker is installed and I use it to create containers and to attach VSCode to them.
I can connect to my remote machine with the Remote-SSH plugin, however I can't attach a VSCode window to the container anymore. It just hangs with this message
The problem was raised by the recent Win11 update I just installed. Is there anything I can do? Tell me if you need more information!
You could try using a private/public key-pair for authentication and on you local machine add the private key to the ssh-agent (which you first need to start in Windows' Services settings) using ssh-add
. That will allow you to connect to the SSH server without additional keyboard input and might avoid the issue you are seeing.
https://github.com/microsoft/vscode-remote-release/issues/7295#issuecomment-1273195599
Had same problem, already answered here. @chrmarti I think it worked without needing ssh keys just a month ago? Only requiring password just like ssh extension without keys.
What do you get for ssh -V
?
local: OpenSSH_7.6p1 Ubuntu-4ubuntu0.7, OpenSSL 1.0.2n 7 Dec 2017 host: OpenSSH_7.6p1 Ubuntu-4ubuntu0.5, OpenSSL 1.0.2n 7 Dec 2017
both are Ubuntu 18.04.6 LTS
Related: https://github.com/microsoft/vscode-remote-release/issues/7322
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
Is this still an issue in the latest version? (We fixed a similar bug in https://github.com/microsoft/vscode-remote-release/issues/7355.)