krallin/tini
A tiny but valid `init` for containers observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 20
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4205
- days_rel: n/a
- days_push: 482
- n_releases_24m: 0
Adoption not part of the score
11220 stars · 546 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Tini is a tiny init system written in C designed to run as PID 1 inside containers. It spawns a single child process, reaps zombie processes, and forwards signals like SIGTERM so containerized applications shut down correctly.
Use cases
- prevent zombie processes in docker containers
- forward SIGTERM to my app in a container
- proper init as pid 1 in docker image
- make docker containers shut down gracefully
- avoid pid exhaustion from zombie processes
- container entrypoint init
When to choose
- you run Docker 1.13+ and want `docker run --init` behavior or a standalone init binary
- your containerized app spawns child processes and lacks its own signal handling
- you need a minimal, dependency-free PID 1 for containers
When to avoid
- your container runs a single process that already handles signals and reaps children
- you use an init system like s6 or dumb-init with features you need beyond simple reaping
- you are not running in a container environment
Facets
cli-tool · maturity stable
container-runtime cli developer-tools developer-tools operating-systems cli init-system zombie-process-reaping signal-forwarding docker-entrypoint pid-1 containers devops linux docker
1 source
- readme: https://github.com/krallin/tini · fetched 2026-08-28 · 594002be4391
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| krallin/tini | main | 32 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem