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.

Sign up for GitHub

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

Jump to bottom

Clone in Volume: Support multiple devcontainer.json files #7879

Open
chrmarti opened this issue Jan 23, 2023 · 3 comments
Open

Clone in Volume: Support multiple devcontainer.json files #7879

chrmarti opened this issue Jan 23, 2023 · 3 comments
Assignees
@chrmarti
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality volume Dev Container mounting a Docker volume
Milestone
Backlog

Comments

@chrmarti
Copy link
Contributor

Continuing from #7548.
@chrmarti chrmarti added containers Issue in vscode-remote containers feature-request Request for new features or functionality labels Jan 23, 2023
@chrmarti chrmarti added this to the Backlog milestone Jan 23, 2023
@chrmarti chrmarti self-assigned this Jan 23, 2023
@chrmarti chrmarti mentioned this issue Jan 23, 2023
Closed
@chrmarti chrmarti added the volume Dev Container mounting a Docker volume label Jan 23, 2023
MikeChurvis added a commit to MikeChurvis/DevContainers that referenced this issue Feb 10, 2023
@MikeChurvis
Reconfigure devcontainers
eb3032b 
At this time VS Code does not support multiple devcontainer definitions in the same repo like GitHub Codespaces does. For this reason, I am forced to use a single devcontainer for this repo containing a unified set of tooling for all projects herein.

This limitation is tracked as an issue here: microsoft/vscode-remote-release#7879
@bamurtaugh bamurtaugh mentioned this issue Apr 24, 2023
Closed
@bilderbuchi
Copy link

To flesh this out a bit: Currently, if you're doing a "Clone repository in named container volume" with a repository that has its devcontainer files in .devcontainer/folderA/devcontainer.json and .devcontainer/folderB/devcontainer.json, you only get to select from the list of standard images -- there is no way to (manually) select the correct json files from the standard location, only to Cancel.

It would be great to either correctly detect and show all present `devcontainer.json´, or let the user manually point to the location of such a file.

@mholttech
Copy link

I was just looking for this myself. Hope to see it soon!

@bilderbuchi
Copy link

Any updates on this?
I just checked with my current version (v0.315.1), and this issue still exists (you only get the list of standard images to select from), meaning one has to copy/duplicate devcontainer files to stand up a correct dev environment. Would it easily be possible to add a "browse for correct file" entry to that list?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chrmarti chrmarti

Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality volume Dev Container mounting a Docker volume
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@bilderbuchi @mholttech @chrmarti