dumb-init
Simple wrapper script which proxies signals to a child
Decision gist · record as of 2026-08-14
Yes, if you run containerized applications as PID 1 and need reliable signal handling and zombie reaping. The package is actively maintained, has no known vulnerabilities, and solves a real problem in container environments. Verify the license terms first if you have commercial or legal constraints.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires a Linux environment with glibc (manylinux wheels provided); not suitable for non-containerized or non-Linux deployments.
- Medium install friction due to platform-specific binary wheels (x86_64, aarch64, ppc64le, s390x).
- The package is actively maintained with recent commits and no known vulnerabilities, though the latest release was in 2022.
License · maintenance · safety
(unclear) — License treatment is unclear from the package metadata, so you should verify the actual license terms in the GitHub repository before adopting it in a commercial or restricted context.
last release 2022-04-26 (1571 days) · last repo commit 2026-07-13 · 7,303 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 455,381 downloads/mo, #6,559 on PyPI
Alternatives
Verify before relying
# Install via pip
pip install dumb-init
# In a Dockerfile, use as PID 1 entrypoint
ENTRYPOINT ["dumb-init", "--"]
CMD ["python", "app.py"]
# Or directly in shell scripts
#!/usr/bin/dumb-init /bin/sh
my-service &
my-other-service- Exact license terms and compatibility constraints for commercial use
- Whether the package works on non-glibc Linux systems or musl-based containers
What it is and what it does
dumb-init is a statically-linked C binary deployed as a Python package that solves two critical problems when running applications as PID 1 inside containers. Normally, when a process becomes PID 1, the Linux kernel applies special signal handling rules: signals without explicit handlers are ignored rather than triggering default behavior, and orphaned zombie child processes are never reaped. This breaks graceful shutdown (SIGTERM has no effect) and leaves defunct processes accumulating in the container.
dumb-init runs as PID 1 and immediately spawns your actual application as a child process. It proxies all signals to that child, which then receives normal signal handling. By default it establishes a process session, so signals reach the entire process tree—useful for shell scripts that spawn background services. It also supports signal rewriting (e.g., converting SIGTERM to SIGQUIT for applications that require a specific stop signal) and can operate in single-child mode for transparent signal forwarding.
Use it for
- Docker containers running shell scripts or multiple background services that need proper signal propagation on shutdown
- Kubernetes or Mesos deployments where the orchestrator sends standard signals but your app requires a different stop signal
- Minimal container images where you want to avoid full init systems like systemd but still need correct process lifecycle handling
- CI/CD pipelines where docker run commands need to cleanly terminate containers without leaving them running in the background
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you run containerized applications as PID 1 and need reliable signal handling and zombie reaping.
The package is actively maintained, has no known vulnerabilities, and solves a real problem in container environments. Verify the license terms first if you have commercial or legal constraints.
Install
dumb-init on PyPI
Before you install
Medium install friction due to platform-specific binary wheels (x86_64, aarch64, ppc64le, s390x). The package is actively maintained with recent commits and no known vulnerabilities, though the latest release was in 2022.
Requires a Linux environment with glibc (manylinux wheels provided); not suitable for non-containerized or non-Linux deployments.
License in practice
License treatment is unclear from the package metadata, so you should verify the actual license terms in the GitHub repository before adopting it in a commercial or restricted context.
Quickstart
# Install via pip
pip install dumb-init
# In a Dockerfile, use as PID 1 entrypoint
ENTRYPOINT ["dumb-init", "--"]
CMD ["python", "app.py"]
# Or directly in shell scripts
#!/usr/bin/dumb-init /bin/sh
my-service &
my-other-serviceVerify before relying
- Exact license terms and compatibility constraints for commercial use
- Whether the package works on non-glibc Linux systems or musl-based containers
Package facts
| License | Not declared unclear |
| Python support | Not specified |
| Install friction | Medium. Platform-specific wheel |
| Runtime dependencies | None |
| Maintenance | Actively maintained 1,571 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 455,381 / month, #6,559 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: dumb_init-1.2.5.post1-py2.py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl; dumb_init-1.2.5.post1-py2.py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl; dumb_init-1.2.5.post1-py2.py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl; dumb_init-1.2.5.post1-py2.py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “container init system”
- dumb-initdumb-init is a minimal init system that runs as PID 1 in containers,…
- wait-for-itA command-line tool that waits for one or more TCP services to become…
- resdataResData reads and writes result files from reservoir simulators,…
Give your agent the search over MCP, or paste the wish link into any chat.
More Utilities packages
Converts domain names between Unicode and ASCII-compatible encoding (Punycode) according to IDNA 2008 and Unicode Technical Standard 46, with security validation and broader script coverage than the standard library.
Install it if you work with internationalized domain names, need to validate domains, or use HTTP clients that depend on it transitively.
Detects and normalizes text encoding from unknown or ambiguous sources, supporting all IANA character sets that Python's core library provides codecs for, with the ability to register custom codecs.
Setuptools is a Python build backend and package management tool that handles building, distributing, and installing Python packages, including support for C/C++ extension modules.
Pluggy provides a plugin system that lets you define hook specifications and register implementations to be called in sequence, enabling extensible Python applications without tight coupling.
Install it if you're building an extensible application or framework.
Pygments is a syntax highlighter that colorizes source code and text in over 500 languages and formats, outputting to HTML, LaTeX, RTF, SVG, images, or ANSI terminal sequences.
Install it if you need to display or transform source code.
Six provides utility functions to write Python code that runs on both Python 2.7 and Python 3.3+, smoothing over language differences between the two versions.
See also pid · tox-docker · simple-pid · cotyledon · blinker · podman-compose · Glances · salt · zc.lockfile · manhole