<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/docker-sandbox-kit-spec-authority-as-code-5x402fi8k" -->

---
title: Docker Sandbox Kit Spec: Authority as Code | daily.dev
description: Docker published the Sandbox Kit Specification v3, an open-source (Apache 2.0) format that packages an AI agent's network rules, credentials, tools, and...
canonical: https://daily.dev/posts/docker-sandbox-kit-spec-authority-as-code-5x402fi8k
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Docker Sandbox Kit Spec: Authority as Code | daily.dev
og:description: Docker published the Sandbox Kit Specification v3, an open-source (Apache 2.0) format that packages an AI agent's network rules, credentials, tools, and...
og:url: https://daily.dev/posts/docker-sandbox-kit-spec-authority-as-code-5x402fi8k
og:image: https://api.daily.dev/og/posts/5X402fI8K.png
og:image:alt: Docker Sandbox Kit Spec: Authority as Code
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Docker Sandbox Kit Spec: Authority as Code

**[Docker](https://daily.dev/sources/docker)** · 9 min read · 1 upvotes · 0 comments

## Summary

Docker published the Sandbox Kit Specification v3, an open-source (Apache 2.0) format that packages an AI agent's network rules, credentials, tools, and volumes as an ordinary, pinnable OCI image called a Kit. Written by Christian Dupuis, the post explains why agent authority needs to be declarative and versioned rather than scattered across shell history and dashboards. A Kit is either a workload (root filesystem) or a mixin (an overlay adding a credential, network rule, or context), composed deterministically via a dependency graph rather than flag order. Declarations act as permission slips read by a conforming runtime, which enforces allow/deny network rules and injects credentials via proxy. Docker Sandboxes is the first conforming runtime, running Kits as microVMs with their own kernel. The spec ships with two conformance suites and is intended to be vendor-neutral, not locked to Docker.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.docker.com/blog/docker-sandbox-kit-spec>

## Questions this post answers

### What is Docker Sandbox Kit Specification v3 and how does it differ from earlier versions?

Sandbox Kit Specification v3 makes a Kit an ordinary OCI image rather than a separate artifact type, with no custom media type or sidecar file. Declarations live in a manifest annotation called vnd.docker.sandbox.kit.descriptor, while layers carry content. This lets a Kit build with docker buildx build, pull with docker pull, and be scanned, signed, and pinned by digest like any container image.

_Teams standardizing agent sandboxing follow spec changes like this one on daily.dev._

### How do Docker Sandbox Kits control what an AI agent is allowed to access?

Each Kit declares typed, versioned capabilities such as network-policy and credential entries that act as a permission slip: allow and deny rules for specific hosts, methods, and paths, with deny always winning over allow. Credentials are proxy-managed, meaning the runtime injects the real token into requests to named domains while the sandbox only sees a sentinel value, preventing the agent from ever holding the raw secret.

_Developers locking down agent permissions can track authority-as-code patterns like this on daily.dev._

### What is the difference between a Docker container and a Docker Sandbox for running AI agents?

A container shares the host kernel and isolates one fixed workload using namespaces and cgroups, which is fine for software that only touches what it was handed. A Docker Sandbox is a microVM with its own kernel, placing the isolation boundary below anything an agent could reach or rewrite, which lets an agent run with root and full autonomy while damage stays contained to the sandbox.

_daily.dev helps engineers evaluating agent isolation options stay current on sandboxing approaches._

## Similar posts on daily.dev

- [Docker Brings Sandbox Kit Spec to the CNCF](https://daily.dev/posts/docker-brings-sandbox-kit-spec-to-the-cncf-s5knbsucl) · Docker · 1 upvotes · 0 comments
- [Why AI Agents Need Isolation with Docker SBX](https://daily.dev/posts/why-ai-agents-need-isolation-with-docker-sbx-maacb8xi9) · Docker · 2 upvotes · 1 comments
- [The Questions Every Team Asks About Docker Sandboxes](https://daily.dev/posts/the-questions-every-team-asks-about-docker-sandboxes-dea3ny4vm) · Cloud Native Now · 0 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#docker](https://daily.dev/tags/docker), [#containers](https://daily.dev/tags/containers)

[View this post on daily.dev](https://daily.dev/posts/docker-sandbox-kit-spec-authority-as-code-5x402fi8k)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Docker Sandbox Kit Spec: Authority as Code","url":"https://daily.dev/posts/docker-sandbox-kit-spec-authority-as-code-5x402fi8k","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/docker-sandbox-kit-spec-authority-as-code-5x402fi8k"},"datePublished":"2026-09-24T16:03:29.251Z","dateModified":"2026-09-24T17:20:29.157Z","description":"Docker published the Sandbox Kit Specification v3, an open-source (Apache 2.0) format that packages an AI agent's network rules, credentials, tools, and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7be8a0db8ab91f7126d8d6f3da0e7f7f?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7be8a0db8ab91f7126d8d6f3da0e7f7f?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Docker","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Docker","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8a1022bebfc04a7d824c309bd3686787","url":"https://daily.dev/sources/docker"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/docker-sandbox-kit-spec-authority-as-code-5x402fi8k","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,docker,containers","timeRequired":"PT9M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Docker","item":"https://daily.dev/sources/docker"},{"@type":"ListItem","position":3,"name":"Docker Sandbox Kit Spec: Authority as Code"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/docker-sandbox-kit-spec-authority-as-code-5x402fi8k#faq","mainEntity":[{"@type":"Question","name":"What is Docker Sandbox Kit Specification v3 and how does it differ from earlier versions?","acceptedAnswer":{"@type":"Answer","text":"Sandbox Kit Specification v3 makes a Kit an ordinary OCI image rather than a separate artifact type, with no custom media type or sidecar file. Declarations live in a manifest annotation called vnd.docker.sandbox.kit.descriptor, while layers carry content. This lets a Kit build with docker buildx build, pull with docker pull, and be scanned, signed, and pinned by digest like any container image. Teams standardizing agent sandboxing follow spec changes like this one on daily.dev."}},{"@type":"Question","name":"How do Docker Sandbox Kits control what an AI agent is allowed to access?","acceptedAnswer":{"@type":"Answer","text":"Each Kit declares typed, versioned capabilities such as network-policy and credential entries that act as a permission slip: allow and deny rules for specific hosts, methods, and paths, with deny always winning over allow. Credentials are proxy-managed, meaning the runtime injects the real token into requests to named domains while the sandbox only sees a sentinel value, preventing the agent from ever holding the raw secret. Developers locking down agent permissions can track authority-as-code patterns like this on daily.dev."}},{"@type":"Question","name":"What is the difference between a Docker container and a Docker Sandbox for running AI agents?","acceptedAnswer":{"@type":"Answer","text":"A container shares the host kernel and isolates one fixed workload using namespaces and cgroups, which is fine for software that only touches what it was handed. A Docker Sandbox is a microVM with its own kernel, placing the isolation boundary below anything an agent could reach or rewrite, which lets an agent run with root and full autonomy while damage stays contained to the sandbox. daily.dev helps engineers evaluating agent isolation options stay current on sandboxing approaches."}}]}
```

