Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple devcontainers not detected when source is in a volume #10740

Open
agrinh opened this issue Feb 27, 2025 · 1 comment
Open

Multiple devcontainers not detected when source is in a volume #10740

agrinh opened this issue Feb 27, 2025 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers

Comments

@agrinh
Copy link

agrinh commented Feb 27, 2025

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

  1. Given a git repository with the following devcontainers:
.devcontainer/
├── gpu
│   └── devcontainer.json
└── cpu
    └── devcontainer.json
  1. Run Dev Containers: Clone Repository in Container Volume
  2. Wait for code to be pulled
  3. Get prompt indicating that no workspace defined devcontainer is found Image
  • 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 Container this 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

@vs-code-engineering vs-code-engineering bot added the containers Issue in vscode-remote containers label Feb 27, 2025
@chrmarti
Copy link
Contributor

A workaround is to have a .devcontainer/devcontainer.json that will be used and once connected use F1 > Dev Containers: Switch Container to switch to a different config.

@chrmarti chrmarti added the bug Issue identified by VS Code Team member as probable bug label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

2 participants