microsoft / microsoft/vscode-remote-release
[Remote - Containers] Be more restrictive when installing Docker Desktop on MacOS to set up a container
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Considering the news that Docker Desktop will require a subscription for anyone working at a large company, it's a bit problematic that this extension tries to help install it when one tries to run a dev container locally.
I would suggest you clearly explain the subscription requirement before offering to install Docker Desktop and/or switch to an alternative implementation, like:
- podman + multipass
- lima
- something you build yourself on top of HyperKit (the VM code that apparently drives Docker Desktop on MacOS)
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
No files or tests are named. Start by tracing the local dev-container setup flow that offers to install Docker Desktop on macOS, then determine where the subscription requirement or an alternative runtime would be presented. Done means users are clearly warned before installation or are offered a supported alternative such as Podman with Multipass or Lima.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, macos, vscode
- Domain
- developer-experience, devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100