microsoft / microsoft/vscode-containers
Auto-detect container runtime when `containers.client` is `Default`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 87
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 9
Description
When the containers.client setting is set to its default, we should try to auto-detect the correct container runtime. We do need to be careful not to regress startup performance though--the overwhelming majority of users use Docker, so a slower startup isn't an acceptable tradeoff.
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 by locating handling for the containers.client setting and the extension's container-runtime startup path. Trace how the default is resolved, then determine how runtime detection can preserve Docker's fast path. Done means the default selects an available runtime without an unacceptable startup slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100