microsoft / microsoft/vscode-containers
[Feature Request] Docker Run Task does not support attached container
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 87
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 9
Description
Context
Consider a project with a C++ development environment that has some associated markdown files that are rendered via MkDocs. The docker image for the development environment is different than the one used to render the MkDocs. Developers wish to render MkDocs using this other image, but need to be able to see build output so they can debug issues.
Current Behavior
The Docker Run task only supports running containers in the detached mode, so the terminal does not attach to the container when it is started via the task.
Current Workaround
Authored a shell script that executes docker run with no --detached flag.
Desired Behavior
The Docker Run task should allow the user to configure if the container should be ran detached.
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 Docker Run task configuration and compare it with the shell script's docker run invocation. Done means users can choose attached or detached execution and attached runs expose build output in the terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100