microsoft / microsoft/vscode-remote-release

Misleading error message when project folder is moved and vscode tries to open it

Open
#7,164 1 comment 0 reactions 1 assignee View on GitHub

@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:

  1. Open project in dev container
  2. Close vscode
  3. Rename/move the project folder
  4. Reopen vscode (automatically tries to open the previous project)
  5. The following message is shown:
    immagine 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.