search

microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
https://aka.ms/vscode-remote
Other
3.66k stars 287 forks source link

Open Folder in Dev Container shows only local folders #7383

Open ilaner opened 2 years ago

ilaner commented 2 years ago

When selecting Open Folder in Dev Container inside a Dev Container, there is no option to select a folder inside the remote environment and only local folders are available. Our use case is to open a Dev Container for the whole project, and have an option to open a different Dev Container for a subdirectory in a new window. It works great if the project has bind mounts, and we select the local path of the folder, but when using Open Dev Container in Volume option the path is unavailable.

Steps to Reproduce:

  1. Connect to a Dev Container
  2. Select Open Folder in Dev Container
  3. The container file system is unavailable.

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

chrmarti commented 2 years ago

Do the subdirectories you want to open have their own devcontainer.json?

ilaner commented 2 years ago

Do the subdirectories you want to open have their own devcontainer.json?

Yes, they have.

vscodenpa commented 2 years ago

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

nelsonjchen commented 1 year ago

This would be extremely useful on macOS as we don't have the capability of cloning to a Linux filesystem with Docker Desktop unlike the WSL and Linux people and taking advantage of performance-toll-free volume mounts to be able to re-open a subfolder of a workspace as a devcontainer itself without going through expensive virtio to the macOS filesystem.

As a result, filesystem heavy repositories that use have multiple devcontainers under them get a serious heavy throughput, latency, and processing penalty on macOS.

vscodenpa commented 1 year ago

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!