microsoft / microsoft/vscode-remote-release
Misleading error message when project folder is moved and vscode tries to open it
Open
@chrmarti is already working on this.
Since Sep 7, 2022.
bug
containers
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.70.2
- Local OS Version: Windows 10
- Remote OS Version: Ubuntu
- Remote Extension/Connection Type: Docker container (with WSL backend)
- Logs:
[44 ms] Remote-Containers 0.245.2 in VS Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662).
[43 ms] Start: Resolving Remote
[65 ms] Setting up container for folder or workspace: [project folder]
[71 ms] Start: Check Docker is running
[72 ms] Start: Run: docker version --format {{.Server.APIVersion}}
[104 ms] spawn C:\Program Files\Docker\Docker\resources\bin\docker.exe ENOENT
[107 ms] Docker returned an error code ENOENT, message: spawn C:\Program Files\Docker\Docker\resources\bin\docker.exe ENOENT
Steps to Reproduce:
- Open project in dev container
- Close vscode
- Rename/move the project folder
- Reopen vscode (automatically tries to open the previous project)
- The following message is shown:
Which suggests in a very misleading way that there is a problem with the docker executable, and gives no clue that the problem is that the project folder has been moved
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.