From f1bef3734517c93f00a8293c288bbed2ea785367 Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Tue, 13 Oct 2026 15:08:43 +0200 Subject: [PATCH] docs: explain the not responding sandbox status (#26301) ## 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 --- content/manuals/ai/sandboxes/troubleshooting.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/content/manuals/ai/sandboxes/troubleshooting.md b/content/manuals/ai/sandboxes/troubleshooting.md index 25580aa683..7e650ef577 100644 --- a/content/manuals/ai/sandboxes/troubleshooting.md +++ b/content/manuals/ai/sandboxes/troubleshooting.md @@ -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 +$ sbx start +``` + +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