opencontainers/runc

CLI tool for spawning and running containers according to the OCI specification

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 18 minutes ago
Added to GitGenius on September 4th, 2026
Created on June 5th, 2015
Open Issues & Pull Requests: 340 (+0)
GitHub issues: Enabled
Number of forks: 2,330
Total Stargazers: 13,436 (+0)
Total Subscribers: 364 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.1 hours
Mean response time: 56.2 days
90th percentile: 30.6 days
Tracked items: 240

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 74% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 3% of issues opened in the past year have been closed. Three people close 61% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 65
New in 7 days: 2
Closed in 7 days: 3
Avg open age: 743 days
Stale 30+ days: 56
Stale 90+ days: 45

Recent activity

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

Top labels

  • kind/bug (24)
  • area/ci (11)
  • regression (11)
  • kind/question (6)
  • llm-generated (5)
  • status/needs-more-information (5)
  • enhancement (4)
  • area/cgroupv1 (3)

Detailed Description

runc is a CLI tool for spawning and running containers on Linux according to the OCI specification.

The tool addresses the need for a standardized, low-level container runtime that implements the Open Container Initiative specification. runc works by taking container configurations and using Linux kernel features to isolate and execute processes. It serves as the reference implementation of the OCI runtime specification, providing a direct interface to container lifecycle operations without requiring a higher-level orchestration layer.

runc is suited for projects that need a lightweight, standards-compliant container runtime, particularly those building container platforms, orchestration systems, or tools that require direct control over container execution. It is the runtime used by Docker and other container engines. The tool supports optional features including seccomp for system call filtering and libpathrs for enhanced path safety during container setup. Adoption requires a Linux system and Go toolchain, with additional build dependencies varying by distribution.

The project maintains signed releases and has undergone third-party security audits. Development activity shows attention to security practices through formal disclosure processes and cryptographic verification of releases. The codebase demonstrates careful dependency management, including support for optional Rust-based components like libpathrs for improved security posture. Build configuration is flexible, allowing developers to customize features and version strings to suit their deployment needs.