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

Please create a CLI and spec for .devcontainer use outside of VSCode #4771

Closed
Taytay opened this issue Mar 26, 2021 · 11 comments
Closed

Please create a CLI and spec for .devcontainer use outside of VSCode #4771

Taytay opened this issue Mar 26, 2021 · 11 comments
Labels
containers Issue in vscode-remote containers *duplicate Issue identified as a duplicate of another issue(s)

Comments

@Taytay
Copy link

Taytay commented Mar 26, 2021

(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?

@github-actions github-actions bot added the containers Issue in vscode-remote containers label Mar 26, 2021
@chrmarti
Copy link
Contributor

Tracked as #4684.

@chrmarti chrmarti added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 29, 2021
@jan-hudec
Copy link

@chrmarti, the requests seem very different. The request #4684 asks for starting vscode with the container opened, while this one asks for starting the container without vscode (UI; though it would be preferable to have just a node library without needing whole installation).

@chrmarti
Copy link
Contributor

Makes sense, reopening to track as separate request.

@chrmarti chrmarti reopened this Mar 29, 2021
@chrmarti chrmarti added feature-request Request for new features or functionality and removed *duplicate Issue identified as a duplicate of another issue(s) labels Mar 29, 2021
@Taytay
Copy link
Author

Taytay commented Mar 30, 2021

Thanks @jan-hudec and thanks @chrmarti for re-opening.
🤞 I'm not alone on this.

@jan-hudec
Copy link

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 devcontainer.json would be significant help (then we could have plugin for the CI that would read the tasks from .vscode/config.json and run them in the devcontainer for near-effortless CI setup).

@PavelSosin-320
Copy link

Plus JSON schema...... if possible.

@baruchiro
Copy link

@chrmarti
Copy link
Contributor

Thanks @baruchiro for the link. Closing as this is now available.

@chrmarti chrmarti removed this from the Backlog milestone Oct 18, 2021
@chrmarti chrmarti added *duplicate Issue identified as a duplicate of another issue(s) and removed feature-request Request for new features or functionality labels Oct 18, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Dec 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

6 participants
@Taytay @jan-hudec @chrmarti @baruchiro @PavelSosin-320 and others