> For the complete documentation index, see [llms.txt](https://devlab-machines.gitbook.io/devlab-machines-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devlab-machines.gitbook.io/devlab-machines-docs/docker-sandbox.md).

# Docker sandbox

The self-hosted coordinator runs outside this app. Repository commands execute in a non-root Docker container with no network, a read-only root filesystem, dropped capabilities, process/memory/CPU limits, and bounded time. No browser worker runs git, builds, or benchmarks.

## Bounds

* Jobs have a database hard deadline of 20 minutes from creation; the worker runs at most 1,000 seconds (`DEVLAB_JOB_SECONDS` may lower this) and checks cancellation with a signed heartbeat every 20 seconds.
* Commands max 180s, measurements 150s, clone 90s, output 1 MB, recipe logs 35 KB each.
* The repository checkout sits on a filesystem quota capped at 256 MB; the worker also monitors checkout size and terminates at this limit.
* `.git` is hidden; harness and dependencies are read-only bind mounts.

Prepare a pinned image containing repository dependencies before disabling network. Executable jobs require the immutable Docker image ID (`sha256:<64 hex>`); mutable tags cannot execute. Missing image, Docker, or configuration records an honest failure — never a sample result.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://devlab-machines.gitbook.io/devlab-machines-docs/docker-sandbox.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.