Open aeschli opened 1 year ago
We remember the last workspace folder used when attaching to a container of a certain image. I guess the folder / workspace is no longer there in the new container. We could look into the container to check if the folder is still there before we reopen the window.
Any luck solving this?
Also running into the same issue here!
This trips me up each time after I try to set up Laravel Sail (Docker-based) project after a break :) In my case, I just need to select the folder in the container that I want to get opened as "workspace":
Version: 1.77.1 Commit: b7886d7461186a5eac768481578c1d7ca80e2d21 Date: 2023-04-04T23:20:37.202Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Linux x64 5.15.0-69-generic snap Sandboxed: No
From our smoke test. Run a doceker with ARM (not sure that really matters)
In the terminal, run:
docker run --privileged --rm tonistiigi/binfmt --install all
docker run -d arm64v8/ubuntu sleep inf
In VS Code, in the Docker viewlet, find the running container and runAttach Visual Studio Code
from the context menu New windows ends with an error dialog: