microsoft / microsoft/vscode-remote-release

Pre-built image not used as-is

Open
#6,558 2 comments 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Apr 4, 2022.

bug containers
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Apologies if this is the wrong place to ask, but would the proposal above address the fact that running devcontainer build followed by devcontainer open opens VS Code but then in the output one of the first things it does is start building stuff again?

[1690 ms] Start: Run: docker events --format {{json .}} --filter event=start
[1692 ms] Start: Run: docker-compose --project-name myproject -f /Users/username/Projects/myproject/docker-compose.yml build

It makes for a very slow startup experience since I cannot interact with the editor until the build completes. What is also non-intuitive for me is that even though it rebuilds after opening the dev container, I am sometimes still prompted that e.g. docker-compose.yml has changed and may need to be rebuilt. How many times does it need to build before VS Code is content that everything is in working shape and can let me get to work?

Originally posted by @jsma in https://github.com/microsoft/dev-container-spec/issues/21#issuecomment-1086338189

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.