Skip to content

WSL2: hyper-v sockets, and VMID #4131

Closed

Description

Please fill out the below information:

  • Your Windows build number: Microsoft Windows [Version 10.0.18917.1000]

  • What you're doing and what's happening:
    I am a member of the Docker Desktop team, working on integration with WSL2. We are using Hyper-V socket as a way to communicate between Windows and Linux processes (as cross-os unix sockets are not available yet on WSL 2). Everything works fine, but retrieving the VMID for setting up the HV-Socket connection requires admin privileges, and finding which running VM is hosting the current user's WSL distros.

  • What's wrong / what should be happening instead:
    We need an API for getting this VMID reliably without admin privileges.

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

Metadata

Assignees

No one assigned

    Labels

    featurewsl2Issue/feature applies to WSL 2

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions