Discovery: sandbox runtime ideas from Daytona (resource limits, warm pools, multi-runner, pluggable backend) #1794

Open
opened 2026-11-07 17:11:49 +00:00 by sam · 0 comments
Owner

What

Daytona (https://www.daytona.io/docs/architecture/) is sandbox infrastructure whose control plane / runner / in-sandbox daemon split mirrors State Store / archied / archie-agent. It covers only the compute half of archie, but several of its runtime features are ones archie lacks. Assess each one and decide whether to adopt it:

  1. Per-task resource limits in the contract. vCPU, RAM and disk are declared on each sandbox and enforced. Today archie has no per-task quota a workflow can set.
  2. Warm pools / snapshots. Pre-started or snapshotted sandboxes so a task doesn't pay full container start cost.
  3. Multiple runners under one control plane. Several runner hosts register with the control plane and get sandboxes placed on them, so capacity can grow past one daemon host.
  4. Pluggable sandbox backend (integration). Check whether archied's container launching sits behind a domain interface clean enough that Daytona (Docker or microVM) could be one implementation. This also supports the goal of not making Docker the only isolation mechanism.

Constraints

  • Task-scoped grants, daemon-only git and egress control must hold on every backend. A remote backend must not get the daemon's credentials.
  • No new binary unless a real process boundary requires one.

Done when

Each of the four items has a recorded verdict (adopt, defer or reject) with a reason. Adopted items are filed as their own feature issues.

## What Daytona (https://www.daytona.io/docs/architecture/) is sandbox infrastructure whose control plane / runner / in-sandbox daemon split mirrors State Store / archied / archie-agent. It covers only the compute half of archie, but several of its runtime features are ones archie lacks. Assess each one and decide whether to adopt it: 1. **Per-task resource limits in the contract.** vCPU, RAM and disk are declared on each sandbox and enforced. Today archie has no per-task quota a workflow can set. 2. **Warm pools / snapshots.** Pre-started or snapshotted sandboxes so a task doesn't pay full container start cost. 3. **Multiple runners under one control plane.** Several runner hosts register with the control plane and get sandboxes placed on them, so capacity can grow past one daemon host. 4. **Pluggable sandbox backend (integration).** Check whether archied's container launching sits behind a domain interface clean enough that Daytona (Docker or microVM) could be one implementation. This also supports the goal of not making Docker the only isolation mechanism. ## Constraints - Task-scoped grants, daemon-only git and egress control must hold on every backend. A remote backend must not get the daemon's credentials. - No new binary unless a real process boundary requires one. ## Done when Each of the four items has a recorded verdict (adopt, defer or reject) with a reason. Adopted items are filed as their own feature issues.
sam added the discoverymedium labels 2026-11-14 14:45:42 +00:00
sam added the deferred label 2026-11-15 17:26:12 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1794