AI Workbench native build failure on Windows 11 + WSL2 + Podman after local service recovery

AI & Data Science NVIDIA AI Workbench
1

If you are reporting a bug or error, consider submitting a Support Bundle to aiworkbench-ea@nvidia.com. This will help us solve your issue more quickly.

Subject

AI Workbench native build failure on Windows 11 + WSL2 + Podman after local service recovery

Summary

We are seeing two related but distinct AI Workbench problems on one workstation:

  1. wb-svc can become unavailable on http://localhost:10001/v1 until the local service is restarted.
  2. After service recovery, native buildProject still fails before a usable build-output.success marker is produced.

The failure is reproducible on two different projects, and validated fallback runtime paths still work, which suggests an AI Workbench lifecycle/orchestration issue rather than a project-payload issue.

Environment

  • Host: BRUTUS
  • Windows: Windows 11 Pro, build 26200
  • AI Workbench desktop app: 0.157.15.7383 (0.157.15-13.7383)
  • WSL CLI: nvwb 0.66.10-4 (full; stable; linux; amd64; go1.24.12; Tue Feb 10 21:27:03 UTC 2026)
  • WSL distro: Ubuntu 22.04.5 LTS
  • Container runtime: Podman 5.4.0
  • GPU: NVIDIA GeForce RTX 4090
  • Driver: 595.79

Reproduced On

  • audio-stable-audio-open
    • native classification: build_output_missing_or_prebuild_orchestration
  • audio-audiogen
    • native classification: audiocraft_git_numstat_poison

Expected Result

  • wb-svc should remain available on http://localhost:10001/v1
  • native buildProject should either complete successfully or report the concrete failing command

Actual Result

  • wb-svc may become unavailable until the local service is restarted
  • after recovery, native buildProject still exits with generic exit status 1
  • no usable build-output.success marker is produced
  • fallback runtime paths remain healthy, which suggests the project payload is viable

Attached Evidence

  • official support bundle: ai-workbench-support-bundle-Kuro-20260417-040917.zip
  • restart_service_probe.json
    • serviceRunning=True | proxyRunning=True | maxCUDAVersion=13.2
  • native_build_audio_stable_audio_open.json
    • classification: build_output_missing_or_prebuild_orchestration
  • native_build_audio_audiogen.json
    • classification: audiocraft_git_numstat_poison
  • runtime_truth_latest.json
    • packaged forges audited: 7
    • divergent: 7

Questions

  1. Is loss of local wb-svc availability on Windows + WSL2 + Podman a known issue?
  2. Why does native buildProject fail before producing a usable build-output.success marker?
  3. Is the AudioCraft git surface only a secondary poison on top of a more general pre-build orchestration problem?

Please tick the appropriate box to help us categorize your post
Bug or Error
Feature Request
Documentation Issue
Other

2

Thank you for reporting this.

  1. This is a known issue but we’ve not been able to pin down an exact pattern.
  2. Will surface this question to engineering.
  3. Same.

Will get back to you.