microsoft / microsoft/vscode-remote-release

Error: spawn ENOTDIR during Devcontainer launch in multi-root workspace if file is named `.code-workspace`

Open
#9,434 0 comments 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Dec 13, 2024.

bug containers
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

  • VSCode Version: 1.85.2 (Universal)

  • Local OS Version: macOS Sonoma 14.2.1 (Darwin arm64 23.2.0)

  • Remote OS Version: Ubuntu "Focal" (20.04.6 LTS)

  • Remote Extension/Connection Type: Containers/WSL/Server

  • Logs:

remoteContainers.log:

[2024-01-24T19:57:25.618Z] Dev Containers 0.327.0 over Remote - SSH 0.107.1 in VS Code 1.85.2 (8b3775030ed1a69b13e4f4c628c612102e30a681).
[2024-01-24T19:57:25.618Z] Start: Run: /bin/sh 
[2024-01-24T19:57:25.705Z] Start: Run in host: echo ~
[2024-01-24T19:57:25.743Z] /home/myuser
[2024-01-24T19:57:25.744Z] 
[2024-01-24T19:57:25.744Z] Stop (39 ms): Run in host: echo ~
[2024-01-24T19:57:25.745Z] Start: Run in host: id -un
[2024-01-24T19:57:25.792Z] myuser
[2024-01-24T19:57:25.792Z] 
[2024-01-24T19:57:25.792Z] Stop (47 ms): Run in host: id -un
[2024-01-24T19:57:25.792Z] Start: Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'myuser' || grep -E '^myuser|^[^:]*:[^:]*:myuser:' /etc/passwd || true)
[2024-01-24T19:57:25.838Z] Stop (46 ms): Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'myuser' || grep -E '^myuser|^[^:]*:[^:]*:myuser:' /etc/passwd || true)
[2024-01-24T19:57:25.840Z] userEnvProbe: loginInteractiveShell (default)
[2024-01-24T19:57:25.840Z] userEnvProbe: not found in cache
[2024-01-24T19:57:25.841Z] userEnvProbe shell: /bin/bash
[2024-01-24T19:57:26.024Z] userEnvProbe PATHs:
Probe:     '/home/myuser/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin'
Container: None
[2024-01-24T19:57:26.594Z] Start: Run: docker version --format {{.Server.APIVersion}}
[2024-01-24T19:57:26.701Z] Stop (107 ms): Run: docker version --format {{.Server.APIVersion}}
[2024-01-24T19:57:26.702Z] 1.43
[2024-01-24T19:57:26.806Z] Error: spawn ENOTDIR
    at T (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1861:5893)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1869:4355
    at async vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1869:2925

Steps to Reproduce:

  1. Create a multi-root workspace with a Devcontainer on a remote machine; name the file .code-workspace; the Devcontainer file does not seem to matter (.devcontainer.json vs. .devcontainer/devcontainer.json vs. .devcontainer/my-profile/devcontainer.json)
  2. Use VS Code remote to launch a Remote-Over-SSH connection to the remote machine
  3. Use VS Code to open the multi-root workspace file (this is successful)
  4. When prompted to reopen in the container, attempt to reopen/rebuild (which will fail).

Does this issue occur when you try this locally?: Unsure (file is hidden by macOS and code .code-workspace opens the file instead of opening the workspace)
Does this issue occur when you try this locally and all extensions are disabled?: Unsure (see above)

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.