Docker Donates Sandbox Kit Spec for Agent Permissions to CNCF

By 作者:Claudio MasoloOriginal title: Docker Sandbox Kit规范:将AI智能体权限打包为OCI镜像
78AI Score

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.

Full Report

Docker announced that it is donating the Sandbox Kit specification to the CNCF, with the goal of making "which resources an AI agent can access" as portable as the agent itself. The specification, licensed under Apache 2.0, has now been upgraded to v3. It packages an agent, the tools it uses, and a typed declaration of the requested hosts, credentials, and volumes into an ordinary OCI image.

Agents like Claude Code and Codex install packages, call APIs, and use credentials on behalf of users. But the authorizations that actually make them work—for example, bind mounts, broad tokens, and opened-up firewall rules—usually end up scattered across shell history, various console dashboards, and people's memories, rather than stored in a reviewable artifact. Docker believes this is exactly the kind of fragmentation that OCI was created to prevent; otherwise, every runtime vendor could invent its own solution.

In v3, a Kit is no longer a separate artifact type. It has no custom media type and no attached sidecar file. Its manifest contains only one declaration: vnd.docker.sandbox.kit.descriptor. As a result, a Kit can be built with docker buildx build, pulled with docker pull, and can be scanned, signed, or referenced in a FROM instruction. Once the digest is pinned, the content and permissions are pinned together.

The declarations are typed, versioned capabilities, such as com.docker.sandbox/network-policy@2 and com.docker.sandbox/credential@1. In the specification's GitHub CLI example, the Kit allows access to api.github.com but denies DELETE operations on /repos/**, because "deny" takes precedence over "allow." Credentials can be hosted by a proxy: a conforming runtime injects the real token into requests sent to the specified domain, while only a sentinel value exists inside the sandbox.

A Kit only "requests" permissions; the host ultimately decides. Without a conforming runtime, the annotation is inert. If a required request cannot be satisfied, startup is refused. Docker Sandboxes (which run agents in microVMs with separate kernels) is the first conforming runtime.

At startup, a workload Kit (which provides the root filesystem) is combined with any number of mixin overlays. Mixins are ordered according to the provides/requires dependency graph, not the order of command-line flags. If a requires is unsatisfied, or if two Kits provide the same name, resolution fails. Overlapping declarations are reconciled: network rules are unioned, while incompatible rules are treated as errors.

Each descriptor can also be reduced to a canonical set of grants. A runtime that gates updates can record this set and block any new version that expands its scope, including versions that remove deny rules. Docker says two conformance test suites ship with the specification, one for Kit artifacts and one for runtimes.

Docker says it is building Kits together with companies including AWS, Box, Datadog, Dynatrace, JFrog, NanoClaw, OpenClaw, Palo Alto Networks, and Snyk. The company compares this to the move that donated the image format and runc, which ultimately led to OCI. CNCF CTO Chris Aniszczyk welcomed the move:

Standards are key to letting an ecosystem move fast without fragmenting, and few companies understand that better than Docker. By delivering Sandbox Kits as standard OCI images, Docker is giving the industry an open, repeatable way to package an AI agent, its tools, and its guardrails as a single artifact.

However, the posts do not state whether the specification has been accepted into a CNCF incubating project, nor which maturity level it will enter.

Engineers who want to try it can visit the docker/sandbox-kit-spec repository, and examples can be tested via the sbx CLI (for example, sbx run ./hello --kit ./gh). Although existing image registries, scanning tools, and signing tools can handle Kits without any changes, the descriptor syntax and the specific semantics of each capability are entirely new and need to be learned. In particular, permission enforcement depends entirely on the runtime. Since Docker Sandboxes is currently the only conforming implementation, portability across different runtimes has not yet been verified. Until the governance structure changes, Docker will continue to maintain the specification and encourages the community to provide feedback on any Kit responsibilities or runtime responsibilities that cannot currently be expressed.

View the original English article: Docker Sandbox Kit Spec: Packaging AI Agent Permissions as OCI Images