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
[Remote-SSH Bug]: "Dev Containers:Attach to Running Container" is not working in a specific server #9064
Comments
I am seeing this exact same bug. My vscode host is an M1 Mac and my ssh target is an ubuntu VM. vscode extension in host machine:
remote-server output:
Edited to add more info. |
I encounter the same problem. The below is logs for vscode extension in host machine.
|
Rollbacking to the |
Could someone explain or link to how I can do this?
edit: Got it. Thanks @microhobby |
Open the Dev Containers extension page in vscode and click the dropdown next to |
Extensions > Dev Containers > Unintall > Install Another Version This comment is easy to understand the way. |
same here, rolled back and it now works... |
it also works in my environment. Thanks a million @microhobby. |
Thank you! It works! |
@connor4312 The I can't reproduce the issue at the moment. Could those seeing it provide additional information on their setup? Please also append the container log from when this happens. ( |
Many thanks @microhobby <3 |
Have the same error with 315/316 versions, had to roll back [12:45:37.099] Resolving exec server at port 50896 [12:45:37.101] [Forwarding server port 50896] Got connection 1 [12:45:37.107] > [12:45:37.112] Exec server for ssh-remote+192.168.1.115 failed: Error: The operation was aborted [12:45:37.112] Error opening exec server for ssh-remote+192.168.1.115: Error: The operation was aborted` |
The local OS might make a difference, got it with the following steps:
Not sure if the |
Moving up to Remote-SSH v0.107.2023092715 avoids the Stack from This seems to be from https://github.com/microsoft/vscode-remote-tunnels/blame/d4789fc7ed4a9b7d428cab28b6d1f24ff27b38df/rpc/src/connectionBearer.ts#L123. |
I encountered this problem today. dev containers works fine when locally connected to the machine, however would crash when networked over wireguard. My logs look identical to mrekin's, except for the following:
|
@connor4312 I don't see this with todays 1.84-Insiders. Does that include a fix in this area? |
Enabling |
This solution worked for me. I was experiencing the same issue and had rolled back to the previous version; which worked. After seeing this comment, I upgraded and tested with |
This solution worked for me as well with the current version of DevContainers extension (v0.315.1) |
A new ssh release will go out shortly that removes the need to manually change the setting |
Deu certo pra mim, gente |
This worked for me as well. I thought I had broken something between switching projects. Thanks ! |
|
This solution is working as well in my enviroment. |
work! |
The fix is now out in Remote - SSH 0.106.5. Took a little longer and there were some additional changes needed.
That's also fixed by this version ^ |
Thank you very much. I can confirm that the problem's gone with Remote - SSH v0.106.5 and Dev Containers v0.315.1.
|
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
settingConnect Locally
It connects successfully
->
I was able to attach to running container until yesterday, but it is suddenly unavailable now.
I got the error message
"Command 'Dev Containers: Attach to Running Container...' resulted in an error
The operation was aborted"
this error message doesn't give me any information about how to deal with this situation.
Also, the error message is invoked before showing the list of running containers.
I can't attach to running container in every server.
I removed the folder "/home/username/.vscode-server", "/home/username/.vscode-remote-containers" to re-initialize the setting of vscode, but it doesn't work.
Expected Behavior
I can choose the running containers in the list. Then I can attach to the running container in a new window.
Steps To Reproduce
No response
Remote-SSH Log
Remote-SSH Log
Anything else?
No response
The text was updated successfully, but these errors were encountered: