VS Code多文件夹工作区启动单Dev Container报‘工作区不存在’求助

问题背景 #

在VS Code多文件夹工作区中启动单个Dev Container时，执行Dev Containers: Rebuild and Reopen in Container会触发"Workspace does not exist"错误，但直接打开根文件夹则能正常运行。需求是通过多文件夹工作区统一管理多个Python仓库，共享通用代码质量配置，无需在各项目中重复设置。

核心原因 #

多文件夹工作区模式下，VS Code会以工作区文件（docker.dev.code-workspace）所在目录作为${localWorkspaceFolder}的指向，但当前Dev Container配置仅挂载了单个项目目录到容器内，导致容器内无法匹配工作区定义的多个文件夹路径，进而触发错误。

解决方案 #

方案1：调整挂载与工作区路径适配 #

修改.devcontainer/service-a/devcontainer.json，将本地根目录完整挂载到容器内，同时指定容器内的工作区路径：

{
  "name": "Service A Development",
  "build": {
    "context": "${localWorkspaceFolder}",
    "dockerfile": "./.devcontainer/service-a/dev.dockerfile"
  },
  "workspaceMount": "source=${localWorkspaceFolder},target=/workspace-root,type=bind,consistency=cached",
  "workspaceFolder": "/workspace-root/sources/service-a",
  "mounts": [
    "source=${localWorkspaceFolder}/standards/python/settings.json,target=/workspace-root/sources/service-a/.vscode/settings.json,type=bind,consistency=cached"
  ],
  "settings": {
    "files.exclude": {
      "/workspace-root/.devcontainer": true,
      "/workspace-root/.vscode": true,
      "/workspace-root/standards": true
    }
  }
}

保持docker.dev.code-workspace的文件夹定义不变，容器内会自动匹配工作区指定的路径。

方案2：将Dev Container配置移到工作区根目录 #

在根目录的.devcontainer下创建统一的devcontainer.json（替代service-a子目录下的配置），确保整个工作区目录都被挂载到容器内：

{
  "name": "Multi-Repo Python Dev Env",
  "build": {
    "context": ".",
    "dockerfile": "./.devcontainer/service-a/dev.dockerfile"
  },
  "workspaceMount": "source=${localWorkspaceFolder},target=/workspace,type=bind,consistency=cached",
  "workspaceFolder": "/workspace",
  "mounts": [
    "source=${localWorkspaceFolder}/standards/python/settings.json,target=/workspace/.vscode/settings.json,type=bind,consistency=cached"
  ]
}

这种方式下，工作区定义的所有文件夹在容器内都能正常访问，无需额外调整路径。

方案3：在工作区文件中指定Dev Container配置路径 #

修改docker.dev.code-workspace，添加配置路径指定，让VS Code在工作区模式下加载正确的Dev Container配置：

{
    "folders": [
        {
            "path": "."
        },
        {
            "path": "sources/service-a"
        }
    ],
    "settings": {
        "dev.containers.configurationPath": "./.devcontainer/service-a/devcontainer.json"
    }
}

同时更新.devcontainer/service-a/devcontainer.json的构建上下文：

{
  "name": "Service A Development",
  "build": {
    "context": "${localWorkspaceFolder}",
    "dockerfile": "./.devcontainer/service-a/dev.dockerfile"
  },
  "workspaceMount": "source=${localWorkspaceFolder}/sources/service-a,target=/workspace,type=bind,consistency=cached",
  "workspaceFolder": "/workspace",
  "mounts": [
    "source=${localWorkspaceFolder}/standards/python/settings.json,target=/workspace/.vscode/settings.json,type=bind,consistency=cached"
  ]
}

验证步骤 #

1. 保存所有配置修改
2. 重新打开docker.dev.code-workspace工作区
3. 执行Dev Containers: Rebuild and Reopen in Container
4. 检查容器内是否能正常访问所有工作区文件夹，以及共享的代码质量配置是否生效

内容的提问来源于stack exchange，提问作者Andez