--- title: Docker Cloud Sandboxes: Recap from WeAreDevelopers description: Docker used WeAreDevelopers World Congress North America to launch Docker Cloud Sandboxes, which let developers start AI agent work locally in an isolated... canonical: https://daily.dev/posts/docker-cloud-sandboxes-recap-from-wearedevelopers-idq93g5x0 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Docker Cloud Sandboxes: Recap from WeAreDevelopers | daily.dev og:description: Docker used WeAreDevelopers World Congress North America to launch Docker Cloud Sandboxes, which let developers start AI agent work locally in an isolated... og:url: https://daily.dev/posts/docker-cloud-sandboxes-recap-from-wearedevelopers-idq93g5x0 og:image: https://api.daily.dev/og/posts/IDQ93g5x0.png og:image:alt: Docker Cloud Sandboxes: Recap from WeAreDevelopers 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 Cloud Sandboxes: Recap from WeAreDevelopers **[Docker](https://daily.dev/sources/docker)** · 11 min read · 0 upvotes · 0 comments ## Summary Docker used WeAreDevelopers World Congress North America to launch Docker Cloud Sandboxes, which let developers start AI agent work locally in an isolated microVM and move longer-running tasks to Docker-managed cloud compute billed by the second. The company also introduced the open Sandbox Kit specification (an OCI image packaging an agent, its tools, and declared access requirements) and committed to contributing it to the CNCF for neutral governance. Keynotes from Docker's COO, CTO, and CISO framed a philosophy of governing the runtime rather than the agent itself, with demos showing blocked actions (a Docker socket escape attempt, a GitHub repo deletion) enforced by sandbox and policy controls. Partner sessions and workshops covered real-world agent deployments, hardened images, and supply chain security for AI-generated code. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Docker Cloud Sandboxes and how does it work with local sandboxes? Docker Cloud Sandboxes lets developers start agent work locally in an isolated microVM using the sbx command-line tool, then move the sandbox's filesystem to Docker-managed cloud compute for longer-running tasks, and bring results back afterward. Each sandbox has its own kernel and Docker daemon. Compute is billed by the second, and local versus cloud credentials and policies are configured separately. _daily.dev surfaces updates like this for developers weighing where to run long agent tasks safely._ ### What is the Docker Sandbox Kit specification? It is an open specification, published under Apache 2.0, defining a Kit as an OCI image that bundles an agent and its tools together with declared access requirements such as credentials, network destinations, and storage. Teams can build, push, pull, scan, and pin Kits by digest using familiar image tooling, and Docker committed to bringing the spec to the CNCF for neutral governance. _developers standardizing agent environments can track specs like this through daily.dev._ ### How does Docker Sandboxes prevent an agent from escaping its container to read host secrets? Docker Sandboxes puts a microVM boundary around the agent rather than relying solely on container isolation. In a demo, an agent running in a container with the host Docker socket mounted was able to read a host secret using granted access, but the same attempt failed when run inside a sandbox, because the microVM enforces the boundary regardless of what the agent tries to do. _teams hardening agent execution against container escapes can follow this kind of security detail on daily.dev._ ## Similar posts on daily.dev - [Building AI Teams with Docker Sandboxes & Docker Agent](https://daily.dev/posts/building-ai-teams-with-docker-sandboxes-docker-agent-mdqr85lrj) · Docker · 2 upvotes · 2 comments - [Everything You Need to Know About Docker AI Sandboxes](https://daily.dev/posts/everything-you-need-to-know-about-docker-ai-sandboxes-j4rxkf9s8) · The Miners · 0 upvotes · 0 comments - [Docker at WeAreDevelopers: Partner & Customer Sessions](https://daily.dev/posts/docker-at-wearedevelopers-partner-customer-sessions-rlvjajrns) · Docker · 2 upvotes · 0 comments - [Docker Isn’t Just About Containers Anymore](https://daily.dev/posts/docker-isn-t-just-about-containers-anymore-86dkmipl5) · SD Times · 1 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#docker](https://daily.dev/tags/docker), [#mcp](https://daily.dev/tags/mcp), [#cncf](https://daily.dev/tags/cncf) [View this post on daily.dev](https://daily.dev/posts/docker-cloud-sandboxes-recap-from-wearedevelopers-idq93g5x0) ```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 Cloud Sandboxes: Recap from WeAreDevelopers","url":"https://daily.dev/posts/docker-cloud-sandboxes-recap-from-wearedevelopers-idq93g5x0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/docker-cloud-sandboxes-recap-from-wearedevelopers-idq93g5x0"},"datePublished":"2026-10-01T18:29:18.255Z","dateModified":"2026-10-04T08:27:58.088Z","description":"Docker used WeAreDevelopers World Congress North America to launch Docker Cloud Sandboxes, which let developers start AI agent work locally in an isolated...","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-cloud-sandboxes-recap-from-wearedevelopers-idq93g5x0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,docker,mcp,cncf","timeRequired":"PT11M"} {"@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 Cloud Sandboxes: Recap from WeAreDevelopers"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/docker-cloud-sandboxes-recap-from-wearedevelopers-idq93g5x0#faq","mainEntity":[{"@type":"Question","name":"What is Docker Cloud Sandboxes and how does it work with local sandboxes?","acceptedAnswer":{"@type":"Answer","text":"Docker Cloud Sandboxes lets developers start agent work locally in an isolated microVM using the sbx command-line tool, then move the sandbox's filesystem to Docker-managed cloud compute for longer-running tasks, and bring results back afterward. Each sandbox has its own kernel and Docker daemon. Compute is billed by the second, and local versus cloud credentials and policies are configured separately. daily.dev surfaces updates like this for developers weighing where to run long agent tasks safely."}},{"@type":"Question","name":"What is the Docker Sandbox Kit specification?","acceptedAnswer":{"@type":"Answer","text":"It is an open specification, published under Apache 2.0, defining a Kit as an OCI image that bundles an agent and its tools together with declared access requirements such as credentials, network destinations, and storage. Teams can build, push, pull, scan, and pin Kits by digest using familiar image tooling, and Docker committed to bringing the spec to the CNCF for neutral governance. developers standardizing agent environments can track specs like this through daily.dev."}},{"@type":"Question","name":"How does Docker Sandboxes prevent an agent from escaping its container to read host secrets?","acceptedAnswer":{"@type":"Answer","text":"Docker Sandboxes puts a microVM boundary around the agent rather than relying solely on container isolation. In a demo, an agent running in a container with the host Docker socket mounted was able to read a host secret using granted access, but the same attempt failed when run inside a sandbox, because the microVM enforces the boundary regardless of what the agent tries to do. teams hardening agent execution against container escapes can follow this kind of security detail on daily.dev."}}]} ```