just-containers/s6-overlay

s6 overlay for containers (includes execline, s6-linux-utils & a custom init)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 15th, 2026
Created on February 28th, 2015
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 240
Total Stargazers: 4,589 (+0)
Total Subscribers: 59 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.9 hours
Mean response time: 33.6 hours
90th percentile: 15.2 hours
Tracked items: 57

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 875 days
Stale 30+ days: 4
Stale 90+ days: 2

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

s6-overlay is a process supervisor and init system for containers that replaces the default Docker entrypoint with s6 as pid 1.

The tool solves the problem of running multiple services reliably within a container while maintaining proper initialization and shutdown sequences. Docker's default behavior of running a single process as pid 1 leaves no room for process supervision, graceful shutdown, or service management. s6-overlay addresses this by providing a complete init system based on s6, a lightweight supervision suite. Installation is straightforward: extract a tarball into your Docker image, and the overlay integrates with your existing setup without requiring image modifications. The system handles multiple init stages, service supervision with automatic restart, logging with log rotation, privilege dropping, and graceful shutdown of all managed services.

The tool suits projects that need to run multiple interdependent services in a single container or require robust process supervision and ordered startup and shutdown sequences. It works on top of any existing Docker image without requiring changes to the base image itself. The README emphasizes compatibility with previous versions and provides migration guidance for users upgrading from earlier releases, indicating that the project maintains backward compatibility as a priority.

Development activity shows consistent maintenance with attention to compatibility across container architectures and careful documentation of upgrade paths. The project provides detailed release notes and upgrade guidance for users migrating between major versions. Build verification is automated, and the maintainers support multiple target architectures with explicit guidance on architecture selection. The project includes comprehensive documentation covering edge cases such as read-only root filesystems, environment variable handling, and performance considerations.