microsoft / microsoft/vscode-remote-release

Trying to open a devcontainer in a remote workspace, when the `.code-workspace` file is local

Open
#8,995 0 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

So, I keep a folder of .code-workspace files for the projects I'm working on. Each of these dictates a remoteAuthority to a remote development server on which we do our work:

as an example, my dune.code-workspace
{
   "folders": [
      {
         "uri": "vscode-remote://ssh-remote+nspawn/home/me/code/dune"
      }
   ],
   "remoteAuthority": "ssh-remote+nspawn",
   "settings": {
      "ocaml.sandbox": {
         "kind": "opam",
         "switch": "${workspaceFolder:dune}"
      }
   }
}

When opening this specific example, since the Dune project has a devcontainer.json, I get this prompt:

image

Unfortunately, it complains about being unable to find the .code-workspace (I assume because it's looking on the remote, not where it's actually located, on my local machine):

image

Ideally, this would "just work" (auto-launching a detected devcontainer, when connected over Remote-SSH, and when the .code-workspace is local) — short of that, a workaround would be appreciated. 😅

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.