NVIDIA / NVIDIA/OpenShell

Sandbox supervisor reports terminal Error phase for a healthy container during GPU-patch recreate

Open
#2,117 3 comments 0 reactions 1 assignee View on GitHub

@elezar is already working on this.

Since Jul 3, 2026.

area:compute area:sandbox state:stale test:e2e topic:compatibility
Dominant language
Rust
Stars
8.7k
Forks
1.3k
Avg merge
2d 11h
Merged PRs (30d)
253

Description

Surfaced via NVIDIA/NemoClaw#5662 (native-Linux GPU onboard). During NemoClaw's GPU-patch recreate (a docker stop + docker run to add device passthrough), openshell sandbox list / get reports the sandbox in a terminal Error phase while the underlying container is running, healthy, and exit_code=0.

NemoClaw only reads the reported phase and its own code documents the ownership boundary: the preferred fix lives at the OpenShell gateway/supervisor, and a NemoClaw-side health-aware retry was explicitly rejected (src/lib/onboard/docker-gpu-supervisor-reconnect.ts). NemoClaw #4316 / #4407 already fixed the classification and timing on the NemoClaw side (the fast-fail message), so this report is specifically the upstream condition.

Expected: the supervisor phase reflects the healthy / recreating container during a stop+run recreate rather than surfacing a terminal Error.

Repro context: native Linux, GPU-enabled sandbox, during the GPU-patch recreate window; reporter diagnostics show phase Error while the container is running/healthy with exit_code=0.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.