containerd/rust-extensions

Rust crates to extend containerd

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

containerd/rust-extensions has 200+ stars and 90+ forks on GitHub, is written in Rust, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 33 minutes ago
Added to GitGenius on October 15th, 2026
Created on June 1st, 2021
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 95
Total Stargazers: 245 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.7 hours
Mean response time: 23.4 days
90th percentile: 74.7 days
Tracked items: 26

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Stale (19)
  • T-CI (3)
  • help wanted (3)
  • C-shim (1)
  • T-bug (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

rust-extensions is a collection of Rust crates that extend containerd with pluggable components for container runtime operations.

The project addresses the need for Rust-based extensions to containerd by providing a modular set of crates covering distinct concerns: protocol bindings for shim interfaces via TTRPC, logging plugins for container shims, a runtime v2 shim wrapper, gRPC client bindings to containerd APIs, remote snapshotter implementations, and a runc CLI wrapper. Developers can use individual crates as needed rather than building these integrations from scratch, reducing boilerplate and ensuring compatibility with containerd's extension interfaces.

The tool suits teams building custom container runtimes, snapshotters, or logging solutions in Rust who want to integrate with containerd. It is particularly valuable for those implementing runtime v2 shims or remote snapshotters, as the crates provide the protocol definitions and wrapper abstractions required by containerd's plugin model. Projects that need to interact with containerd via gRPC or implement container lifecycle hooks will find the client and shim crates most relevant. The modular design means you can adopt only the crates your project requires.

The project targets the latest stable Rust version and requires protoc to be available during builds, as several crates generate protocol bindings at build time. Development activity shows consistent maintenance of the crate ecosystem with updates to keep pace with Rust toolchain changes and containerd API evolution.