microsoft / microsoft/vscode-remote-release
Trying to open a devcontainer in a remote workspace, when the `.code-workspace` file is local
Nobody has claimed this yet.
- 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:
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):
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
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.
Assessment
This issue has not been assessed yet.