microsoft / microsoft/vscode-remote-release
Multiple devcontainers not detected when source is in a volume
Open
@chrmarti is already working on this.
Since Feb 27, 2025.
bug
containers
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.97.2 (Universal)
- Local OS Version: macOS 15.1.1 (24B2091)
- Remote OS Version: Ubuntu 20.04.6 LTS
- Remote Extension/Connection Type: Dev Containers
- Logs: N/A
Steps to Reproduce:
- Given a git repository with the following devcontainers:
.devcontainer/
├── gpu
│ └── devcontainer.json
└── cpu
└── devcontainer.json
- Run
Dev Containers: Clone Repository in Container Volume - Wait for code to be pulled
- Get prompt indicating that no workspace defined devcontainer is found
- Expected: A choice of workspace defined devcontainers gpu or cpu
- Note: When not using a container volume, i.e. with code already pulled locally or on a remote machine, and using
Dev Containers: Open Folder in Containerthis works as expected with the same repo.
Does this issue occur when you try this locally?: No (with local source tree instead of a container volume)
Does this issue occur when you try this locally and all extensions are disabled?: N/A
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.