> ## Content Index
> Fetch the complete content index at: https://www.stirup.si/llms.txt
> Use this file to discover other available public pages before exploring further.

# Trust Docker for the agents you don’t
- URL: https://www.stirup.si/trust-docker-for-the-agents-you-dont-bcb983b4/
- Published: 2026-10-12T08:55:23.000Z
- Updated: 2026-10-12T15:32:35.000Z
- Description: Docker's Cloud Sandboxes and open Sandbox Kit specification aim to provide developers with secure, isolated environments for running agents, while enabling governance and control across local and cloud workflows.
- Author: Satish Das
- Tags: Infrastructure, Stirup Research

## Overview of Docker's Cloud Sandboxes and Sandbox Kit

Docker has introduced Cloud Sandboxes, a new feature designed to allow developers to run agent-based tasks in isolated microVM environments. This capability extends the existing local sandboxing tools, enabling developers to move workloads from their laptops to the cloud seamlessly. The Cloud Sandboxes feature is part of a broader initiative to establish a foundation for trust in agent-based workflows, with a focus on containment, control, and governance.

## Isolation and Execution Boundaries

At the core of Docker's approach is the use of microVMs to isolate agent workloads. Each sandbox operates as a separate microVM with its own kernel and Docker daemon, ensuring that agents cannot access resources outside their designated environment. This isolation is critical for preventing unintended interactions, such as agents accessing sensitive host files or configurations. The use of microVMs provides a stronger boundary than traditional containers, which are typically run within a shared kernel.

## Open Sandbox Kit Specification

Docker has also introduced the Sandbox Kit specification, an open standard for defining agent environments. A Kit is an OCI image that includes the agent, its tools, and declarations of the access it requires. This specification allows teams to share and review environment configurations, ensuring that permissions and dependencies are explicitly defined and auditable. The specification is published under the Apache 2.0 license and is being submitted to the Cloud Native Computing Foundation (CNCF) for neutral governance.

## Workflow and Governance

The Cloud Sandboxes workflow supports a hybrid approach, where developers can start tasks locally and then move them to the cloud for extended execution. This flexibility is particularly useful for tasks that require more compute resources or longer runtime than a local machine can provide. The same Kit-based agent packages work in both environments, ensuring consistency and reducing the overhead of managing separate configurations.

## Security and Policy Enforcement

Docker emphasizes that the infrastructure itself enforces boundaries, even when agents attempt to act outside their defined permissions. This includes runtime enforcement of policies, such as blocking unauthorized network destinations or preventing agents from performing actions like deleting repositories. These controls are implemented at the runtime layer, ensuring that governance is consistent across different agent tools and models.

## Community and Ecosystem Integration

Docker has partnered with various organizations, including Nous Research and Spectro Cloud, to demonstrate the practical application of these tools. These collaborations highlight the potential for integrating Cloud Sandboxes and Sandbox Kits into broader development and security workflows. The Docker Pavilion at WeAreDevelopers provided a platform for customers, partners, and developers to discuss real-world use cases and challenges in deploying and governing agent-based systems.

## Conclusion

Docker's Cloud Sandboxes and Sandbox Kit specification represent a significant step toward enabling secure, scalable, and governed agent-based workflows. By providing isolation, open standards, and runtime enforcement, Docker aims to address the challenges of trust and control in modern development environments. These tools are now available for use, with compute billed by the second, offering developers a practical way to manage agent workloads across local and cloud environments.

**Source:** [Docker](https://www.docker.com/blog/docker-cloud-sandboxes-wearedevelopers-recap/?ref=stirup.si). Analysis based on publicly available information; no hands-on testing is claimed.