s6-overlay is a production-grade init system and process supervisor for Docker containers, built on top of the s6 ecosystem (s6, s6-rc, s6-linux-init). It replaces the default container PID 1 with a robust supervision tree that handles zombie reclamation, orderly startup/shutdown, service dependencies, and logging. The architecture is layered: stage0 (s6-linux-init-maker) generates stage1 infrastructure at runtime, stage2 (rc.init) compiles s6-rc service databases and brings up services via s6-rc, supporting both legacy /etc/services.d directories and modern s6-rc source definitions. The system provides utilities like with-contenv (inject container environment), logutil-service (privilege-dropped logging), and with-retries (retry with timeout). It handles edge cases such as read-only root filesystems, non-root USER directives, and Kubernetes world-writable /run configurations. The codebase is predominantly shell and execline scripts, with a Makefile-based build system that cross-compiles all skaware dependencies statically. It is actively maintained, with a clear separation of concerns and extensive documentation derived from the actual code behavior.
phusion/baseimage-docker is a specialized Ubuntu base image optimized for Docker containers. It solves common Docker container problems including the PID 1 zombie reaping issue (via a custom /sbin/my_init process), syslog blackhole problem (using syslog-ng that forwards logs to docker logs), and APT incompatibilities. The image provides service supervision through runit, tools for running processes as different users (setuser), easy SSH access (optional), and environment variable management. It's designed to be used as a base image for Docker applications, offering a minimal but production-ready Ubuntu environment.
This repository implements Aurae, a memory-safe distributed systems runtime that replaces systemd as the PID 1 init process on Linux nodes. It manages workloads (processes, containers, VMs) with cgroups v2 isolation, eBPF-based observability, and a gRPC API defined via protobuf. The system consists of three main binaries: auraed (daemon), auraescript (TypeScript scripting runtime), and aer (CLI). It also provides a partial Kubernetes CRI implementation and supports nested cells for multi-tenant isolation. The codebase is in early active development with many incomplete features and ignored tests, but demonstrates strong architectural patterns such as proc-macro-driven code generation, a reusable validation framework, and an eBPF abstraction layer. It is not production-ready.