containers/crun

A fast and lightweight fully featured OCI runtime and C library for running containers

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 50 minutes ago
Added to GitGenius on September 16th, 2026
Created on September 13th, 2017
Open Issues & Pull Requests: 49 (+0)
GitHub issues: Enabled
Number of forks: 449
Total Stargazers: 4,131 (+0)
Total Subscribers: 51 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.8 hours
Mean response time: 15.5 days
90th percentile: 14.5 days
Tracked items: 243

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 77% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 88% of issues opened in the past year have been closed, leaving a working backlog. Three people close 79% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 30
New in 7 days: 1
Closed in 7 days: 3
Avg open age: 488 days
Stale 30+ days: 19
Stale 90+ days: 14

Recent activity

Opened in 7 days: 1
Closed in 7 days: 3
Comments in 7 days: 11
Events in 7 days: 21

Top labels

  • bug (1)
  • enhancement (1)
  • good first issue (1)
  • kind/feature (1)

Detailed Description

crun is a lightweight OCI runtime written in C that executes containers according to the Open Container Initiative specification.

The tool addresses the need for a fast, minimal-footprint container runtime that can run on resource-constrained environments including IoT devices and embedded systems. It implements the full OCI runtime specification while maintaining a smaller memory footprint and faster startup time compared to alternatives. The project provides both a standalone runtime executable and a C library that can be embedded in other applications, allowing developers to integrate container execution capabilities directly into their own software.

Developers should choose crun when targeting environments where resource efficiency matters—embedded systems, IoT deployments, or scenarios where startup latency is critical. The dual nature as both a runtime and a library makes it suitable for projects that need programmatic container control rather than just command-line execution. The C implementation distinguishes it from runtimes written in heavier languages, making it particularly valuable for systems with strict memory or CPU constraints.

The project maintains steady development activity with regular commits addressing bug fixes, performance improvements, and feature additions. Pull requests receive timely review and feedback from maintainers. The codebase shows active maintenance with issues being tracked and resolved, and the project continues to evolve in response to user needs and OCI specification updates.