everruns-integrations-docker 0.16.0

Docker container integration for Everruns agents
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

# everruns-integrations-docker

> Session-scoped Docker container execution for Everruns agents.

[![Crates.io](https://img.shields.io/crates/v/everruns-integrations-docker.svg)](https://crates.io/crates/everruns-integrations-docker)
[![Documentation](https://docs.rs/everruns-integrations-docker/badge.svg)](https://docs.rs/everruns-integrations-docker)
[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/everruns/everruns/blob/main/LICENSE)

`everruns-integrations-docker` gives agents a Docker container tied to the
session lifecycle. The container starts lazily on first tool use, and agents can
run commands, read and write files, and stop it when done — a self-hosted way to
give an agent a real execution environment.

Part of the [Everruns](https://everruns.com) ecosystem — the durable agentic
harness engine for building unstoppable agents. It registers with `everruns-core`
through the Everruns integration plugin system.

## Quick Example

```rust
use everruns_core::capabilities::Capability;
use everruns_integrations_docker::DockerContainerCapability;

let capability = DockerContainerCapability;

assert_eq!(capability.id(), "docker_container");
```

## What It Provides

- A session-scoped Docker container, lazily started on first use
- `docker_exec` for running commands in the container
- `docker_read_file` and `docker_write_file` for in-container file access
- `docker_stop` to tear the container down
- Inventory-based Everruns integration registration

## Documentation

- [API reference (docs.rs)](https://docs.rs/everruns-integrations-docker)
- [Everruns documentation](https://docs.everruns.com)

## License

Licensed under the [MIT License](https://github.com/everruns/everruns/blob/main/LICENSE).