microsoft / microsoft/vscode-remote-release
Wrong WSL instance chosen for auto-mount
@chrmarti is already working on this.
Since Aug 8, 2024.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Version: 1.92.0 (user setup)
Commit: b1c0a14de1414fcdaa400695b4db1c0799bc3124
Date: 2024-07-31T23:26:45.634Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22621
Remote OS Version: Alpine 3.20.0 (Docker Desktop)
Remote Extension/Connection Type: Containers + WSL
Steps to Reproduce:
- Install any distro on WSL.
- Install Docker Desktop (or presumably Podman Desktop)
- Ensure that the default distro is not the docker/podman distro
- Attempt to set up a devcontainer.
When attempting to start a container - including recovery containers - and the default distro is anything other than the actual target distro, the wrong distro is chosen for the "auto" mounts like X11/wayland.
Obviously, this can be worked around by changing the default distro, or disabling the auto mounting behavior, but this is unfriendly. Preferably the extension could detect the correct distro and respond accordingly.
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
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.