-
Notifications
You must be signed in to change notification settings - Fork 292
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
Please create a CLI and spec for .devcontainer use outside of VSCode #4771
Comments
Tracked as #4684. |
Makes sense, reopening to track as separate request. |
Thanks @jan-hudec and thanks @chrmarti for re-opening. |
I would add that for me the main reason to want this is continuous integration. When I set up a devcontainer for development, I obviously want to use the same container for CI. Being able to just load the parameters from |
Plus JSON schema...... if possible. |
Thanks @baruchiro for the link. Closing as this is now available. |
(I couldn't find anything related to this in the issues list, but there likely is one.)
Short version: This project is attempting to do what I'm hoping Microsoft will make officially supported:
https://github.com/stuartleeks/devcontainer-cli
Longer version: I love the
.devcontainer
approach, and want to see it adopted and standardized everywhere. I am adding it to a popular open source project right now. My only hesitation is the notion that it requires VSCode. I'd love to be able to offer everyone a fallback of a CLI tool that allows for the common use cases from the command line:Starting/stopping container
Dropping into the container
Running a command
etc...
For this to happen, the
.devcontainer
needs to be a separate spec defined and captured outside of a VSCode extension. Is that on the roadmap? Perhaps that's very publicly described as a goal somewhere, and I just missed it?The text was updated successfully, but these errors were encountered: