HOT RADAR
agentHEAT 11.8°

AI CURATED HOT STORY · 11/16/2026

Docker Donates Sandbox Kit Spec for Agent Permissions to CNCF

1 reports archived1 independent sourcesupdated 11/16/2026, 16:49:00
Synthesis & Latest Updates
1 Sources Cross-Validated

Docker has donated its Sandbox Kit specification to CNCF and upgraded it to v3, packaging an agent, its tools, and a typed manifest of requested hosts, credentials, and volumes into a plain OCI image so permissions can be built, pulled, scanned, and signed like any container. The Apache 2.0 spec expresses permissions as typed, versioned capabilities adjudicated by the host, though Docker Sandboxes is currently the only compliant runtime and cross-runtime portability remains unproven.

LATEST/Docker has donated its Sandbox Kit specification to CNCF and upgraded it to v3, packaging an agent, its tools, and a typed manifest of requested hosts, credentials, and volumes into a plain OCI image so permissions can be built, pulled, scanned, and signed like any container. The Apache 2.0 spec expresses permissions as typed, versioned capabilities adjudicated by the host, though Docker Sandboxes is currently the only compliant runtime and cross-runtime portability remains unproven.

Hourly heat curve

2 fully observed hours
Fewer than 3 fully observed hours; trend not plotted yet.

Coverage timeline

Total 1 reports · Latest first
  1. InfoQ 中文T2·78 pts
    • Sandbox Kit v3 is no longer a separate artifact type: no custom media type or sidecar, just a vnd.docker.sandbox.kit.descriptor declaration, buildable via buildx and pullable, scannable, and signable
    • Permissions are typed, versioned capabilities such as com.docker.sandbox/network-policy@2 and credential@1, with deny rules overriding allow, and credentials proxied so only a sentinel value exists inside the sandbox
    • Kits only request permissions while the host adjudicates; Docker Sandboxes is the sole compliant runtime today and cross-runtime portability is unverified