docs: clarify Windows socket failures during Sandboxes daemon startup

[Gazz-gg]

Description

Document the Windows daemon startup failure involving an inaccessible internal Unix socket. The troubleshooting page currently moves from a daemon restart to resetting state without identifying this case.

Add the recognizable error, diagnostic information to retain, and guidance to state preservation requirements when reporting the failure. A socket error alone does not establish that sandbox data is corrupted. This change does not prescribe relocating LOCALAPPDATA or claim a runtime fix.

Related issues or tickets

• stuck socket sbx-releases#640
• sandboxd v0.30.0 on Windows: in-process moby backend cannot self-connect to its own docker.sock ("Cannot connect to the Docker daemon at unix://...docker.sock") sbx-releases#157

Validation

• Applied against current main at 31d174d.
• rumdl 0.2.49: changed Markdown file passes, using this repository's configuration.
• Vale 3.17.0: changed file checked with the synchronized Docker style package.
• git diff --check passes.
• Full-site build and full validation matrix were not run locally; only one troubleshooting file changes.

Reviews

• Technical review
• Editorial review

Supporting recorded comparison: docker/sbx-releases#640 (comment)

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	b5ae4e2
🔍 Latest deploy log	https://app.netlify.com/projects/docsdocker/deploys/6ad27b654a6e18c60c9e8bce
😎 Deploy Preview	https://deploy-preview-26369--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.