Skip to content

Wrong WSL instance chosen for auto-mount #10147

Open

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:

  1. Install any distro on WSL.
  2. Install Docker Desktop (or presumably Podman Desktop)
  3. Ensure that the default distro is not the docker/podman distro
  4. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

containersIssue in vscode-remote containersinfo-neededIssue requires more information from poster

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions