microsoft / microsoft/vscode-remote-release

`Rebuild Container` fails for broken multi root Workspace Container

Open
#6,790 7 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Description

  • VSCode Version: 1.67.2
  • Local OS Version: Ubuntu 20.04.4
  • Remote OS Version: Ubuntu 20.04.4
  • Remote Extension/Connection Type: Containers
  • Remote - Containers v0.234.0

In #387 and #1258 it was added that you can open workspaces directly in containers. If the creation of the container is successful, Rebuild Container works and the container gets rebuilt. If the build is unsuccessful and you then try Rebuild Container in that window, nothing happens except that it tries to activate extensions. With normal containers, however, this works without problems.

Steps to Reproduce:

  1. Use any multi root workspace with a docker file that fails during build
  2. Remote-Containers: Open Workspace in Container
  3. Cancel the popup
  4. Remote-Containers: Rebuild Container

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

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.