Containers

Container management capability — no backend wired yet

Container capabilities are declared in the API but have no backend today, so every call raises NotImplementedError.

Quick Start

1. What happens when you call it

   Every container function raises immediately — no container is created.

   # Explicit import — container_create is intentionally hidden from __all__ until a backend lands
   from praisonai.capabilities import container_create
   
   try:
       result = container_create("python:3.11")
   except NotImplementedError as e:
       print(e)
       # container_create has no backend implementation yet. Container
       # management is not wired to a provider, so no container is actually
       # created. Track/implement this before relying on it.

2. Run code in a container instead

   To actually run code in an isolated container today, use Docker with an agent.

   from praisonaiagents import Agent
   
   agent = Agent(
       name="Docker Runner",
       instructions="Run tasks inside a Docker sandbox"
   )
   
   agent.start("Summarise the latest AI research")

   See Run on Docker for the supported path.

How It Works

The CLI and MCP adapters wrap these calls and surface an honest error: the CLI exits non-zero, and MCP returns an error instead of a fake container ID.

Configuration Options

No options apply while there is no backend. The signature is retained for a future provider.

Common Patterns

Isolated execution is available through supported paths instead:

• Docker sandbox — run agent tasks inside a container with Run on Docker.
• Sandboxed tools — restrict tool execution with the sandbox configuration.

Best Practices

Related