multirun
A minimalist init process designed for Docker (by nicolas-van)
tini
A tiny but valid `init` for containers (by krallin)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
multirun
Posts with mentions or reviews of multirun.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-25.
-
Systemd by Example
I recently switched to multirun [1] which in my case is superior to supervisor. I don't have to create any config files anymore, and it behaves exactly as i want it to: If one on the processes dies the complete container will die and docker's restart-policy takes place.
[1] https://github.com/nicolas-van/multirun
tini
Posts with mentions or reviews of tini.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-30.
- Anakin – Automatically Kill Orphans
-
Freenginx.org
yes busybox httpd or civetweb is even smaller, both around 300kb.
for tini you mean https://github.com/krallin/tini? how large is your final docker image, why not just alpine in that case which is musl+busybox
-
🚨Avoid this when running containerized applications in production
Tini, a useful process manager for containerized apps
-
Should You Be Scared of Unix Signals?
Ah gotcha. I believe it can be baked into images as well, per the entrypoint example in the readme: https://github.com/krallin/tini
Not sure how this will fare IRL in k8s as I haven’t much experience there. It’s still silly that this is the default behavior where you need something like Tini, but I digress.
-
The Tailscale Universal Docker Mod
To be fair, even for running a single process the pitfalls are real. I've been seeing Tini[1] a lot for these situations.
I just read in the README that Tini is included by Docker since 1.13 if using --init flag.
[1] https://github.com/krallin/tini
-
docker run --init flag doesn't seem to work on Mac
The default init process used is the first docker-init executable found in the system path of the Docker daemon process. This docker-init binary, included in the default installation, is backed by tini.
- ส่อง Dockerfile for Go
- Learning by doing: An HTTP API with Rust
-
Silver bullet: selfhostable personal knowledge management system
AFAIK It's for the init process to reparent zombie processes. See TINI
-
How to implement pods that gracefully shutdown
The second easiest (and most common when your entry point is a bash script) is to use a fake init tool like tini
What are some alternatives?
When comparing multirun and tini you can also consider the following projects:
docker-centos7-systemd-unpriv - Dockerfile for CentOS7 with Systemd in unprivileged mode
dumb-init - A minimal init system for Linux containers