Repository navigation
Sandbox supervisor reports terminal Error phase for a healthy container during GPU-patch recreate #2117
Description
Activity
Investigation confirms that the reported
Errorphase can result from the Docker driver observing both the stopped backup and the healthy replacement with the same sandbox identity labels, then selecting the stopped container for the cached snapshot.PR #2116 is related, but should not yet be treated as the fix. This issue and the changes proposed in #2116 raise a broader ownership question: should matching, copyable Docker labels be sufficient for an out-of-band container to become the authoritative driver-managed instance?
Note that this is also not GPU-specific and affects any out-of-band container modifications.
Maintainer status ping: NVIDIA/NemoClaw#5662 is currently a v0.0.75 test blocker and is waiting on this OpenShell issue. Is there a confirmed fix path or ETA we can align the release train to? If another issue or PR now owns the work, please point us there. Thanks.
- added a commit that references this issue
on Aug 19, 2026 This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.
Surfaced via NVIDIA/NemoClaw#5662 (native-Linux GPU onboard). During NemoClaw's GPU-patch recreate (a
docker stop+docker runto add device passthrough),openshell sandbox list/getreports the sandbox in a terminalErrorphase while the underlying container is running, healthy, andexit_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
Errorwhile the container is running/healthy withexit_code=0.