feat(resources): implement container tool execution engine using Docker SDK #8612

Open
opened 2026-04-13 21:15:17 +00:00 by HAL9000 · 0 comments
Owner

Metadata

  • Commit message type: feat
  • Scope: resources
  • Branch name prefix: feat/v3.6.0-container-tool-execution

Background and Context

As part of Epic #8568 (Resource Types & Container Tool Execution), tools must be able to execute within Docker containers for isolation. This enables tools that require specific environments (e.g., a specific Python version, a specific OS) to run safely.

This issue blocks Epic #8568.

Expected Behavior

  • Tools can be configured to execute within a Docker container
  • Container execution is configurable: image, volumes, environment variables, timeout
  • Container output is captured and returned to the tool caller
  • Container execution is isolated (no access to host filesystem beyond configured volumes)

Acceptance Criteria

  • ContainerExecutor class is implemented using Docker SDK
  • Container execution is configurable: image, volumes, env vars, timeout
  • Container output (stdout/stderr) is captured and returned
  • Container execution is isolated (no host filesystem access beyond volumes)
  • Integration tests verify container execution with a real Docker container
  • Unit tests achieve >= 97% coverage

Subtasks

  • Implement ContainerExecutor class using Docker SDK
  • Add container configuration schema (image, volumes, env, timeout)
  • Implement output capture (stdout/stderr)
  • Implement isolation enforcement (no host filesystem access)
  • Write integration tests for container execution
  • Write unit tests for ContainerExecutor

Definition of Done

  1. Container tool execution engine is implemented
  2. Integration tests verify container execution
  3. Unit tests pass with >= 97% coverage
  4. Code reviewed and merged to main branch

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Metadata - **Commit message type**: `feat` - **Scope**: `resources` - **Branch name prefix**: `feat/v3.6.0-container-tool-execution` ## Background and Context As part of Epic #8568 (Resource Types & Container Tool Execution), tools must be able to execute within Docker containers for isolation. This enables tools that require specific environments (e.g., a specific Python version, a specific OS) to run safely. This issue blocks Epic #8568. ## Expected Behavior - Tools can be configured to execute within a Docker container - Container execution is configurable: image, volumes, environment variables, timeout - Container output is captured and returned to the tool caller - Container execution is isolated (no access to host filesystem beyond configured volumes) ## Acceptance Criteria - [ ] `ContainerExecutor` class is implemented using Docker SDK - [ ] Container execution is configurable: image, volumes, env vars, timeout - [ ] Container output (stdout/stderr) is captured and returned - [ ] Container execution is isolated (no host filesystem access beyond volumes) - [ ] Integration tests verify container execution with a real Docker container - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Implement `ContainerExecutor` class using Docker SDK - [ ] Add container configuration schema (image, volumes, env, timeout) - [ ] Implement output capture (stdout/stderr) - [ ] Implement isolation enforcement (no host filesystem access) - [ ] Write integration tests for container execution - [ ] Write unit tests for ContainerExecutor ## Definition of Done 1. Container tool execution engine is implemented 2. Integration tests verify container execution 3. Unit tests pass with >= 97% coverage 4. Code reviewed and merged to main branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.6.0 milestone 2026-04-13 21:18:26 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#8612
No description provided.