Skip to content

Allow 'custom' (subdirectory) .devcontainer.json to be started #8753

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

Open
gbraad opened this issue May 14, 2025 · 0 comments
Open

Allow 'custom' (subdirectory) .devcontainer.json to be started #8753

gbraad opened this issue May 14, 2025 · 0 comments

Comments

@gbraad
Copy link

gbraad commented May 14, 2025

🌈 Feature

At the moment only the default .devcontainer/devcontainer.json is used, but this in my case points to .devcontainer/default/devcontainer.json. I have multiple setup definitions, as is possible with Codespaces. Since the default is used, this causes a problem on startup, as at the moment #8752 prevents a start. An alternative would be to allow a more 'barebones' defintion, or allow a default (configurable) path to consider, like .devcontainer/codesandbox/ if exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant