Docker Feature Trails

Feature trailActive

AI Agent Isolation and Secure Execution

This feature thread tracks Docker's advancements in providing secure and isolated execution environments for AI agents. Initially, the focus was on the growing need for isolation as AI agents shifted from passive assistance to active code execution. Subsequent posts detail Docker's solutions, including Docker SBX (Sandboxes) which leverages microVMs for enhanced security, and Sandbox Kits for creating reusable, standardized, and secure AI development environments. This post elaborates on the expansion of Cloud Sandboxes, which provide a microVM boundary for agents to run longer tasks in the cloud, and introduces the open Sandbox Kit specification for defining agent environments and their access needs, with a commitment to bring it to the CNCF. It also details how runtime governance, rather than agent-specific governance, is key to managing AI agent activity across an organization, with a focus on security controls and auditability.

26 posts · 2026

Timeline

Feature trailActive

Developer Productivity and Security Tooling

This feature thread tracks Docker's evolution in providing tools and guidance to enhance developer productivity and security. Initially, the focus was on core containerization capabilities and community engagement. Subsequent posts detail advancements in areas like secure execution environments (e.g., Docker SBX, Sandbox Kits), improved build processes (e.g., Docker Bake, SBOM generation), and the integration of security best practices directly into the development workflow. This post introduces the use of Docker Sandboxes (sbx) for AI-assisted firmware development, enabling safe, isolated, and hardware-in-the-loop workflows for AI agents working on ESP32 projects. It details how to combine Docker images for reproducible builds with sandboxes for unsupervised AI sessions, including network serial bridging for flashing and monitoring.

6 posts · 2026

Timeline

Feature trailActive

Extended Lifecycle Support for End-of-Life Software

This feature thread tracks Docker's Extended Lifecycle Support (ELS) offering, designed to provide ongoing security patches, compliance, and audit readiness for end-of-life (EOL) software components. Initially focused on addressing the risks associated with EOL software in production environments, subsequent posts detail the expansion of ELS to cover various components like MinIO, Nginx, Node, and Python. This post details the migration of Minimus customers to Docker Hardened Images (DHI) and highlights the addition of MinIO as a maintained, hardened image under ELS, emphasizing Docker's commitment to backporting CVE fixes and providing audit evidence for archived projects.

3 posts · 2026

Timeline

Feature trailActive

Docker VMM

This feature thread tracks Docker's advancements in its virtualization layer for Docker Desktop. Initially, the focus was on the need for a performant and stable VM to run the Linux-native Docker engine on macOS and Windows. Subsequent posts detail the development and release of Docker VMM, a first-party virtualization layer built from the ground up by Docker. This post announces the public beta of Docker VMM, highlighting significant performance improvements in container startup, file I/O, and memory management, and its integration with Docker Sandboxes (SBX).

1 post · 2026

Timeline

Feature trailActive

OIDC for CI/CD Authentication

This feature thread tracks Docker's advancements in secure authentication for CI/CD pipelines. Initially, the focus was on eliminating stored credentials in CI/CD workflows. Subsequent posts detail the introduction of OpenID Connect (OIDC) support for GitHub Actions, allowing organizations to authenticate with short-lived, per-run tokens instead of static secrets. This enables enhanced security by reducing the risk of credential leakage and simplifying credential rotation.

1 post · 2026

Timeline

Feature trailActive

EU AI Act Compliance

This feature thread tracks Docker's efforts to help customers comply with the EU AI Act. Initially, the focus was on understanding the Act's requirements and its phased rollout. Subsequent posts detail specific obligations for different risk tiers, transparency requirements for generative AI, and the compliance timeline. This post elaborates on the detailed obligations for providers and deployers of high-risk AI systems, including risk management, data governance, technical documentation, and post-market monitoring. It also details the transparency obligations for limited-risk systems, such as deepfake labeling and synthetic content marking, and the compliance timeline with the Digital Omnibus adjustments.

1 post · 2026

Timeline