tinyhumansai/openhuman · error
Docker execution failed: {e}
Error message
Docker execution failed: {e} What it means
docker_exec failed at the spawn/IO level (Ok(Err(e)) from running the container command) — the container never produced output. Typically Docker not running, the image missing, or a daemon/permission problem, as opposed to the command inside the container failing.
Source
Thrown at src/openhuman/sandbox/docker.rs:176
let exit_code = output.status.code().unwrap_or(-1);
tracing::debug!(
exit_code = exit_code,
stdout_len = stdout.len(),
stderr_len = stderr.len(),
"[sandbox:docker] container exited"
);
Ok(SandboxExecResult {
exit_code,
stdout,
stderr,
timed_out: false,
})
}
Ok(Err(e)) => {
tracing::error!(error = %e, "[sandbox:docker] failed to spawn container");
anyhow::bail!("Docker execution failed: {e}")
}
Err(_) => {
tracing::warn!(
timeout_secs = request.timeout.as_secs(),
"[sandbox:docker] container timed out, killing"
);
Ok(SandboxExecResult {
exit_code: -1,
stdout: String::new(),
stderr: format!(
"Command timed out after {}s and was killed",
request.timeout.as_secs()
),
timed_out: true,
})
}
}
}View on GitHub (pinned to 7491200858)
Solutions
- Start Docker and confirm `docker info` works
- Pull the sandbox image if it is missing
- Fall back to the local OS jail backend if Docker is unavailable
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at src/openhuman/sandbox/docker.rs:176 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/6909f67c0f5139af.
Report an issue: GitHub.