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
An extra "Could not fetch remote environment error" when there's an issue with remote connection #135392
Comments
Same issue here. I am looking at running docker without Docker Desktop in Windows, and I have a following setup as docker compose that I start before attaching:
After the docker compose is up, attaching VS code to the As Docker Desktop is no longer free of charge for commercial users, I would assume many people might start switching off using it for development, and therefore might browse the possibility of running docker without Docker Desktop, and thus could be seeing the same errors. It'll be great if such error can be fixed; or if it is not a bug, maybe help us resolve our problem. Thanks! |
@MikaelUmaN Are you using Docker Desktop for Windows or some other type of installation? Is the problem still present using VS Code Insiders? (https://code.visualstudio.com/insiders/) @zhongjie-cai How did you install Docker? |
I am using Docker Desktop latest version. I have had this problem for quite a while so I don't know that things would work better in the insider version. I will give it a try when I can. Can you tell me how I can provide more diagnostic info for you guys? |
@Tyriar This error message seems to originate from terminal code. Is there a way to diagnose this further? |
I'm having a similar error. Can't start my WSL Ubuntu distro in VS Code, but it works fine through Powershell / cmd. Same error messages. EDIT: Solved my issue. VM was missing network connectivity. I turned on debugging for the extension (Settings -> Extensions > Remote - WSL) and got this in the terminal after reloading VS Code: Log
I went into the VM and tried to find the VS Code extension files and eventually noticed that the machine didn't have network connectivity. Which led me to this microsoft/WSL#5336 (comment). Now the machine has network connectivity and I can access the VM through VS Code. |
@chrmarti you could check why
null
|
I see @alexdima Can we add logging for these two cases? If we are hitting this code path too often for logging each time, we could maybe throw / propagate an error and log it in those cases where this is fatal. |
@Tyriar I think I added the |
@chrmarti would a silent error be good here? Normally all terminals that fail launch show a notification |
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! |
@alexdima |
Yes, the error is logged and handled somewhere else. But in our system we have tens of callers to When I implemented terminal reconnection last year I was not familiar enough with the terminal code-base in order to handle the |
Issue Type: Bug
5 ...
Then:
A) Start container xyz
B) Attempt attach in vs code
Expected:
Actual:
VS Code version: Code 1.60.1 (83bd43b, 2021-09-10T17:07:10.714Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
Fetching remote diagnostics for 'Container lyn-repo-01.brummer.se:8181/dr/jupyter-dotnet-datascience:latest (data)' failed: WebSocket close with status code 1006
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Fetching remote diagnostics for 'Container lyn-repo-01.brummer.se:8181/dr/jupyter-dotnet-datascience:latest (data)' failed: WebSocket close with status code 1006
A/B Experiments
The text was updated successfully, but these errors were encountered: