microsoft / microsoft/vscode-remote-release
`Rebuild Container` (without reopening) from outside of DevContainer
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
I would like the ability to rebuild my DevContainer without attempting to reopen it. When iterating on the DevContainer itself, it's very jarring to constantly be transitioning between in and out of the DevContainer, having the log pop up when it fails, etc. My present work around is to look at the Container Log, find the docker build command being invoked, and manually execute that. Using the devcontainer CLI would presumably provide the same functionality, but I'm hoping for the option to do this via the same VSCode commands I'm used to interacting with for my DevContainer workflow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing VS Code DevContainer commands and the Container Log, then compare their docker build flow with the devcontainer CLI entry point mentioned in the issue. Done means a VS Code command can rebuild the DevContainer from outside it without reopening the container or relying on manually copied docker build commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100