docker-wrapper

A type-safe Docker CLI wrapper for Rust.

Installation

[dependencies]
docker-wrapper = "0.10"
tokio = { version = "1", features = ["full"] }

MSRV: 1.89.0

Quick Start

use docker_wrapper::{DockerCommand, RunCommand, StopCommand, RmCommand};

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    // Run a container
    let container = RunCommand::new("nginx:alpine")
        .name("my-nginx")
        .port(8080, 80)
        .detach()
        .execute()
        .await?;

    println!("Started: {}", container.short());

    // Stop and remove
    StopCommand::new("my-nginx").execute().await?;
    RmCommand::new("my-nginx").execute().await?;

    Ok(())
}

Note: Import DockerCommand trait to use .execute() on commands.

Features

# Docker Compose support
docker-wrapper = { version = "0.10", features = ["compose"] }

# Container templates (Redis, PostgreSQL, etc.)
docker-wrapper = { version = "0.10", features = ["templates"] }

Compose Example

use docker_wrapper::{DockerCommand, compose::{ComposeUpCommand, ComposeDownCommand, ComposeCommand}};

ComposeUpCommand::new()
    .file("docker-compose.yml")
    .detach()
    .execute()
    .await?;

Templates Example

use docker_wrapper::{RedisTemplate, Template};

let redis = RedisTemplate::new("my-redis")
    .port(6379)
    .password("secret");

let id = redis.start().await?;
redis.stop().await?;

Why docker-wrapper?

This crate wraps the Docker CLI rather than calling the Docker API directly (like bollard).

Choose docker-wrapper when: You're building CLI tools, need Compose support, want to work with Docker alternatives, or are migrating shell scripts to Rust.

Choose bollard when: You need maximum performance, direct API access, or are building a long-running service with many Docker operations.

Documentation

• API Reference - Complete documentation with examples
• Examples - Working code examples

License

MIT OR Apache-2.0