Docker adds agent-focused building blocks to Compose

Docker announced agent-focused building blocks for Docker Compose, describing a compose.yaml-based way to define models, agents, and MCP-compatible tools together.

By Hypler editorial team · Source: Docker.

Original source date: .

Hypler publication: . Hypler updated: .

Estimated reading time: 4 minutes.

Topics: Docker, Compose, agents, MCP

Docker logo

Generated editorial illustration: separate compute, storage and cooling modules in a cutaway appliance.
Generated editorial illustration: separate compute, storage and cooling modules in a cutaway appliance. Credit: Hypler / AI-generated editorial illustration. Hypler editorial asset

Compose was presented as a packaging layer

Docker announced agent-focused building blocks for Docker Compose on July 10, 2025. The article described using compose.yaml to define open models, agents, and MCP-compatible tools, then starting them with docker compose up. It named examples involving LangGraph, Embabel, Vercel AI SDK, Spring AI, CrewAI, Google's ADK, and Agno. It also described MCP Catalog and Model Runner integrations plus cloud deployment integrations for Google Cloud Run and Microsoft Azure Container Apps. The announcement positions Compose as declarative packaging for agent stacks, not as a substitute for their security or release design.

Topology should be a reviewable operating artifact

A Compose definition should show services, images, commands, ports, networks, volumes, environment variables, health checks, resource limits, dependency order, and profiles. Give each service a clear role: model endpoint, agent runtime, retrieval index, MCP server, gateway, or observability collector. Pin production-intended images by digest and build local images from declared revisions. Named networks should express intended communication; remove default connectivity a service does not need. The resolved manifest becomes executable documentation for design, security, and operations review, including the paths a model-enabled service can actually reach.

Environment separation should reveal rather than hide drift

Keep environment-specific values in reviewed layers instead of copying whole Compose files. A base topology can describe relationships and schemas while overlays supply hosts, digests, limits, and secret-store references. Generate or inspect the resolved configuration in CI so reviewers can compare the actual development, test, and release topology. Treat changes to ports, mounts, capabilities, networks, and credentials as first-class diffs. This preserves portability while exposing each environment's real boundary. A passing local stack cannot demonstrate that a release profile has the same restrictions without this resolved evidence.

A local retrieval stack demonstrates the pattern

Consider a hypothetical stack with an agent runtime, read-only retrieval service, MCP gateway, and documentation-search server. Compose pins each image, puts the agent behind the gateway, exposes retrieval only on an internal network, and mounts synthetic fixtures read-only. The agent may call one search tool through the gateway; it has no credentials for source writes or deployment. Health checks wait for index and gateway before startup. A test profile uses deterministic fixtures and records tool calls. This makes the service graph and its intended limits visible before a broader environment is considered.

Secrets, storage, and networks need owners

Reference secrets through a designated secret mechanism or runtime injection path, never image layers or committed environment files. Map every volume to data owner, retention rule, backup need, and permitted writer. Define outbound destinations for model APIs, identity providers, registries, and external tools, then validate those routes at runtime. Run services with the lowest practical privileges and use read-only filesystems where writes are unnecessary. These controls prevent a convenient multi-service definition from quietly widening access to hosts, records, or credentials. They also give incident responders a map of where evidence and state can persist.

Validate the resolved graph and its failures

Inspect resolved Compose configuration and run named services together. Cover clean startup, health-check failure, unavailable model endpoint, invalid tool output, missing secret, denied network route, corrupted index, restart, and duplicate task request. Confirm logs carry service identity and correlation identifiers across agent, gateway, and tool server. Measure startup, memory, CPU, latency, and outcome categories under fixtures. Record profile, resolved file, image digests, environment identifiers, and outputs so a unit-focused run cannot be mistaken for full integration. Hypler's view is that declarative packaging earns trust through this evidence, not through portability alone. It also makes later change review materially faster for accountable operators.

Hypler analysis

Hypler’s view

Declarative packaging can make an agent stack reproducible, yet it concentrates decisions about models, tools, mounts, networks, and secrets into configuration. A portable file is useful evidence only when the resolved topology and its behavior have been reviewed.

Hypler technical analysis

Engineering notes

A compose.yaml can express models, agents, MCP tools, networks, volumes, and environment wiring as a reproducible application graph. That makes configuration a primary review artifact: apparently local changes can alter an endpoint, expose a secret, persist data, or create new reachability between services.

What to inspect

Service graph
Inspect each service image, command, dependency, port, network, volume, health condition, and declared relationship to model or tool services.
Configuration provenance
Identify every environment variable and secret reference, its source, intended consumer, rotation path, and behavior when missing or malformed.
Reproducibility test
Bring up the declared stack in a controlled environment; inspect resolved images, effective configuration, denied network paths, and validation output for intended workflows.

Scope and limits. Declarative packaging can improve inspection and repeatability. A portable compose file does not document approval, dependency trust, permissions, or successful validation by itself. Resolved runtime configuration remains the artifact to review before an environment is used.

Terms and definitions

MCP
Model Context Protocol, an open protocol for connecting AI applications to tools, data sources, and prompts through defined interfaces.
MCP Gateway
A service boundary that routes MCP traffic and can apply discovery, authentication, authorization, and policy controls.
Tool Calling
A model interface pattern where the model requests a structured operation from an external tool.
API Layer
The server-side interface that exposes defined data and actions to clients or integrations.

More on this subject

Generated illustration of isolated tool-execution fixtures and a controlled test gate; not deployed software.
Generated illustration of isolated tool-execution fixtures and a controlled test gate; not deployed software. Credit: Hypler / AI-generated editorial illustration. Hypler editorial asset; not vendor or event photography

Original source

Historical source briefing with Hypler engineering analysis. Source details reflect the original publication date; implementation examples are hypothetical. Technical analysis expanded October 24, 2026; this does not change the original source event or establish a new source verification. Editorial prose revised October 26, 2026; original event, publication and source-check dates are retained.

Related capabilities