Skip to content

[WSLC] Allow commands to receive input #1258

Closed

Description

Description of the task

Via WslcGetProcessIOHandle (https://wsl.dev/api-reference/c/process-apis/wslcgetprocessiohandle/)

&

typedef enum WslcProcessIOHandle
{
    WSLC_PROCESS_IO_HANDLE_STDIN = 0,
    WSLC_PROCESS_IO_HANDLE_STDOUT = 1,
    WSLC_PROCESS_IO_HANDLE_STDERR = 2
} WslcProcessIOHandle;

https://wsl.dev/api-reference/c/enumerations/wslcprocessiohandle/

Additional context

No response

Release tracking

Allow programs in WSLC to receive input from a file, pipe, or SDK, both when starting a new container and when running a command in an existing container. Reopened to track this unfinished implementation rather than create a duplicate issue. The SDK prerequisite is no longer blocked.

Keep this issue open until both input-forwarding PRs are merged. #1562 is part of the work; the final PR, #1564, closes the issue.

Activity

  1. added
    Issue-TaskEngineering, maintenance, or operational work that is not a bug or feature request.
    on Sep 23, 2026
  2. SohamDas2021 commented on Sep 24, 2026

    @SohamDas2021
    Contributor

    I was already tracking this in ADO and this is blocked on WSLC SDK. Context below:

    WslcGetProcessIOHandle(WSLC_PROCESS_IO_HANDLE_STDIN) returns E_INVALIDARG. CreateRelayedProcessIO creates and relays a stdin pipe, but only when WSLCProcessFlagsStdin is set (otherwise it closes stdin outright), and wslc exec -i sets it, which is why the CLI has working stdin and we don't.

    The gap looks confined to the SDK layer: CopyProcessSettingsToRuntime leaves WSLCProcessOptions::Flags unset under a // TODO: No user access, and WslcProcessSettings exposes no setter for it, so no SDK caller can reach stdin.

    Reached out to WSLC SDK team- microsoft/WSL#41695

  3. changed the title [-]WSLc state-aware daemon should expose native STDIO handles[/-] [+][WSLC] [BLOCKED ON WSLCSDK] State-aware daemon should expose native STDIO handles[/+] on Sep 24, 2026
  4. added
    Priority2High-impact issue affecting key functionality; prioritize for the next appropriate release.
    on Sep 24, 2026
  5. SohamDas2021 commented on Sep 24, 2026

    @SohamDas2021
    Contributor

    Tracked in ADO

  6. changed the title [-][WSLC] [BLOCKED ON WSLCSDK] State-aware daemon should expose native STDIO handles[/-] [+][WSLC] Allow commands to receive input[/+] on Oct 27, 2026
  7. added
    OS-WindowsApplies specifically to Windows hosts or Windows behavior.
    Area-Rust-SDKPublic Rust SDK APIs and integration with the MXC execution engine.
    Area-Node-SDKNode.js and TypeScript SDK APIs, bindings, packaging, CLI integration, or tests.
    Backend-WSLCWindows WSL Container backend behavior or integration.
    In-PRThe issue has an associated pull request in progress.
    Area-DotNet-SDK.NET SDK APIs, native bindings, packaging, samples, or tests.
    and removed
    Priority2High-impact issue affecting key functionality; prioritize for the next appropriate release.
    on Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Area-DotNet-SDK.NET SDK APIs, native bindings, packaging, samples, or tests.Area-Node-SDKNode.js and TypeScript SDK APIs, bindings, packaging, CLI integration, or tests.Area-Rust-SDKPublic Rust SDK APIs and integration with the MXC execution engine.Backend-WSLCWindows WSL Container backend behavior or integration.In-PRThe issue has an associated pull request in progress.Issue-TaskEngineering, maintenance, or operational work that is not a bug or feature request.OS-WindowsApplies specifically to Windows hosts or Windows behavior.

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions