fix(onboard): warn on Docker GPU sandbox DNS failure#5539
Conversation
Signed-off-by: HwangJohn <angelic805@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdds an optional post-recreate external DNS probe to the Docker GPU sandbox patch path. After recreating the container, ChangesDocker GPU sandbox post-recreate external DNS probe
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Signed-off-by: HwangJohn <angelic805@gmail.com>
Signed-off-by: HwangJohn <angelic805@gmail.com>
Summary
Adds a best-effort DNS probe after Docker GPU sandbox recreation so users get a clear warning when the patched sandbox cannot resolve external domains. The probe is diagnostic only and does not switch network modes, inject DNS settings, or fail onboarding by itself.
Related Issue
Refs #5520
Changes
NEMOCLAW_DOCKER_GPU_PATCH_DNS_PROBE=0as a probe opt-out.Type of Change
Verification
Validated locally on Windows and on DGX Spark/Linux.
npm run docscompleted with 0 errors; Fern reported the existing 2 warnings.Verifiedin GitHubnpx prek run --from-ref main --to-ref HEADpassesnpm testpasses (broad runtime changes only)npm run docsbuilds without warnings (doc changes only)Signed-off-by: HwangJohn angelic805@gmail.com
Summary by CodeRabbit
Documentation
getent hostsdiagnostics and remediation steps (fix Docker DNS and recreate sandbox, or temporarily enable host networking).New Features
Tests