docker/docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-10-23 18:09:02 +03:00
Code Activity

docs: explain the not responding sandbox status (#26301)

Browse Source 
## Summary

Explain the `running (not responding)` status shown by `sbx ls` and how
to restart the affected sandbox while keeping saved files.

The status was introduced in
[docker/sandboxes#6111](https://github.com/docker/sandboxes/pull/6111).
[docker/sandboxes#6778](https://github.com/docker/sandboxes/pull/6778)
extends detection to command execution and file transfer. The entry
documents the visible status and recovery without diagnosing the
underlying failure or implying that it is common.

Changed Markdown passes rumdl and Vale. Kept in draft for [Sandboxes
v0.48.0](https://github.com/docker/sandboxes/issues/7014).

@netlify /ai/sandboxes/troubleshooting/#sandbox-is-not-responding

Generated by Codex
This commit is contained in:
David Karlsson
2026-10-13 15:08:43 +02:00
committed by GitHub
parent 8ac30aaec4
commit f1bef37345
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
content/manuals/ai/sandboxes/troubleshooting.md
View File

@@ -28,6 +28,19 @@ with suggested fixes. Use `--output json` to get machine-readable output, or
`--output github-issue` to generate a Markdown snippet suitable for pasting
into a GitHub issue.
## Sandbox is not responding
If `sbx ls` shows `running (not responding)`, Docker Sandboxes has detected
that the sandbox isn't responding to commands. Stop and start that sandbox,
then retry your command:
```console
$ sbx stop <SANDBOX_NAME>
$ sbx start <SANDBOX_NAME>
```
Files saved in the sandbox are kept when you stop and start it.
## Restart the sandbox daemon
If sandbox commands hang, fail to connect to the daemon, or keep returning