Two failures this covers — identify yours first:
| What you see | Which section |
|---|---|
Every sbx command fails: "daemon not reachable" / sbx diagnose shows Daemon=fail |
Symptom A (daemon down) |
Daemon is fine, most sandboxes work, but one sandbox won't start: failed to start shim … shim exited before creating pipe: exit status 1 |
Symptom B (zombie shim / pipe collision) |
Golden rules: Your sandbox data lives on disk in containerd — a daemon restart or an OS reboot never loses it. Never run sbx reset to troubleshoot; it wipes every sandbox and isn't needed for either failure below.