microsoft / microsoft/vscode-remote-release
Docker: No obvious way to use an existing image
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Let's say my org has a generic image, called development-base.
The extension seems to want me to define a custom Dockerfile. If I do so, I can say FROM development-base and be done, but then VS Code will attempt to build that image by sending my entire working copy to the Docker daemon.
I think there should be straightforward support for just specifying an existing image tag/URL. Note that this is not attaching to a "running container"; I want VS Code to spawn a new container from the given image.
Firstly, is this possible, and secondly, should we make it more obvious in the UX?
Thanks
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 reviewing issue #4229 and the repository's existing dev-container configuration and UX entry points; no specific files or tests are named in the report. Confirm how an existing image tag or URL could launch a new container without sending the working copy for a build, and identify how that option should be exposed. Done means the workflow is supported and clearly discoverable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100