mirror of
https://github.com/qwibitai/nanoclaw.git
synced 2026-06-27 18:34:58 +08:00
Omri Maya
1d6bba4d3f
Pass CONTAINER_CPU_LIMIT / CONTAINER_MEMORY_LIMIT through to `docker run` as --cpus / --memory in buildContainerArgs. Both default to empty, so spawn args are byte-identical to today unless an operator opts in — no risk of OOM-ing existing workloads. Caps an agent container's CPU/memory so one agent can't monopolize the host. Swap is a deployment concern (--memory is a hard cap on a swapless host); not managed here. Structural tests assert each flag is pushed and guarded by its env knob, matching the existing buildContainerArgs structural-test convention. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
NanoClaw Documentation
The official documentation is at docs.nanoclaw.dev.
The files in this directory are original design documents and developer references. For the most current and accurate information, use the documentation site.
| This directory | Documentation site |
|---|---|
| SPEC.md | Architecture |
| SECURITY.md | Security model |
| REQUIREMENTS.md | Introduction |
| docker-sandboxes.md | Docker Sandboxes |
| APPLE-CONTAINER-NETWORKING.md | Container runtime |