Docker Agent
- ID
- 33222
- Status
- summarized
- Published
- 08 Oct 2026, 1:48 AM
- Fetched
- 08 Oct 2026, 10:07 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://github.com/docker/docker-agent
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 08 Oct 2026, 10:07 PM
- Tags
- Audience
- developersai_agent_usersvibe_codersai_ml_learners
What happened
Docker Engineering has open-sourced docker-agent (Apache-2.0, 4.1k stars, 491 forks), a Docker CLI plugin that defines AI agents in declarative YAML and runs them via `docker agent run agent.yaml`. It supports multi-agent teams with delegation, any MCP server as a toolset, provider-agnostic models (OpenAI, Anthropic, Gemini, AWS Bedrock, Mistral, xAI, Docker Model Runner), built-in think/todo/memory tools, and pluggable RAG with BM25, embeddings, hybrid search and reranking. Agents can be pushed to and pulled from any OCI registry, and the plugin requires Docker Desktop 4.63+; the HN thread drew 264 points and 121 comments.
Why it matters
If you already run Docker Desktop 4.63+, you can try this without new infrastructure, and the OCI push/pull path means agents become versioned, shareable artifacts instead of scripts living in someone's repo — which changes how you'd ship an internal agent to teammates or clients. The MCP toolset support also lets you reuse existing MCP servers rather than rewriting tool integrations per framework, so the concrete decision is whether your next agent is YAML-defined and registry-distributed or stays as code in a framework like LangGraph.
Discussion angle
Is packaging agents as OCI images a real distribution win, or does a YAML DSL hit a ceiling the moment you need custom control flow — and what does the 121-comment HN thread actually say about that tradeoff?