{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/564", "result": {"data":{"issuesJson":{"id":"a6d421b8-6e35-5f5b-a3da-ed4ccf0ebdfe","title":"krallin/tini: 一个最小化的 init 系统，运行在容器内部，用于启动一个子进程，并等待进程退出时清理僵尸和执行信号转发。","number":564,"bodyHTML":"
\n



\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Reposkrallin/tini
Views\"views\"
Stars\"stars\"
Forks\"forks\"
License\"license\"
UpdatedAt\"last-commit\"
CreatedAt\"create-at\"
\n\n

\"\"

\n\n
\n\n

Tini - A tiny but valid init for containers

\n

\"Build

\n

Tini is the simplest init you could think of.

\n

All Tini does is spawn a single child (Tini is meant to be run in a container),
\nand wait for it to exit all the while reaping zombies and performing
\nsignal forwarding.

\n

Why Tini?

\n

Using Tini has several benefits:

\n\n

If you'd like more detail on why this is useful, review this issue discussion:
\nWhat is advantage of Tini?.

\n

Using Tini

\n

NOTE: If you are using Docker 1.13 or greater, Tini is included in Docker
\nitself. This includes all versions of Docker CE. To enable Tini, just pass the
\n--init flag to docker run.

\n

NOTE: There are pre-built Docker images available for Tini. If
\nyou're currently using an Ubuntu or CentOS image as your base, you can use
\none of those as a drop-in replacement.

\n

NOTE: There are Tini packages for Alpine Linux and NixOS. See below for
\ninstallation instructions.

\n

Add Tini to your container, and make it executable. Then, just invoke Tini
\nand pass your program and its arguments as arguments to Tini.

\n

In Docker, you will want to use an entrypoint so you don't have to remember
\nto manually invoke Tini:

\n
# Add Tini\nENV TINI_VERSION=v0.19.0\nADD https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini /tini\nRUN chmod +x /tini\nENTRYPOINT [\"/tini\", \"--\"]\n\n# Run your program under Tini\nCMD [\"/your/program\", \"-and\", \"-its\", \"arguments\"]\n# or docker run your-image /your/program ...\n
\n

Note that you can skip the -- under certain conditions, but you might
\nas well always include it to be safe. If you see an error message that
\nlooks like tini: invalid option -- 'c', then you need to add the --.

\n

Arguments for Tini itself should be passed like -v in the following example:
\n/tini -v -- /your/program.

\n

NOTE: The binary linked above is a 64-bit dynamically-linked binary.

\n

Signed binaries

\n

The tini and tini-static binaries are signed using the key 595E85A6B1B4779EA4DAAEC70B588DFF0527A9B7.

\n

You can verify their signatures using gpg (which you may install using
\nyour package manager):

\n
ENV TINI_VERSION v0.19.0\nADD https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini /tini\nADD https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini.asc /tini.asc\nRUN gpg --batch --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 595E85A6B1B4779EA4DAAEC70B588DFF0527A9B7 \\\n && gpg --batch --verify /tini.asc /tini\nRUN chmod +x /tini\n
\n

Verifying binaries via checksum

\n

The tini and tini-static binaries have generated checksums (SHA1 and SHA256).

\n

You can verify their checksums using sha1sum and sha256sum (which you may install using
\nyour package manager):

\n
ENV TINI_VERSION v0.19.0\nRUN wget --no-check-certificate --no-cookies --quiet https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini-amd64 \\\n    && wget --no-check-certificate --no-cookies --quiet https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini-amd64.sha256sum \\\n    && echo \"$(cat tini-amd64.sha256sum)\" | sha256sum -c\n
\n

Alpine Linux Package

\n

On Alpine Linux, you can use the following command to install Tini:

\n
RUN apk add --no-cache tini\n# Tini is now available at /sbin/tini\nENTRYPOINT [\"/sbin/tini\", \"--\"]\n
\n

NixOS

\n

Using Nix, you can use the following command to install Tini:

\n
nix-env --install tini\n
\n

Debian

\n

On Debian (Buster or newer), you can use the following command to install Tini:

\n
apt-get install tini\n
\n

Note that this installs /usr/bin/tini (and /usr/bin/tini-static), not /tini.

\n

Arch Linux

\n

On Arch Linux, there is a package available on the AUR.
\nInstall using the official instructions
\nor use an AUR helper:

\n
pacaur -S tini\n
\n

Other Platforms

\n

ARM and 32-bit binaries are available! You can find the complete list of
\navailable binaries under the releases tab.

\n

Options

\n

Verbosity

\n

The -v argument can be used for extra verbose output (you can pass it up to
\n3 times, e.g. -vvv).

\n

Subreaping

\n

By default, Tini needs to run as PID 1 so that it can reap zombies (by
\nrunning as PID 1, zombies get re-parented to Tini).

\n

If for some reason, you cannot run Tini as PID 1, you should register Tini as
\na process subreaper instead (only in Linux >= 3.4), by either:

\n\n

This will ensure that zombies get re-parented to Tini despite Tini not running
\nas PID 1.

\n

NOTE: Tini will issue a warning if it detects that it isn't running as PID 1
\nand isn't registered as a subreaper. If you don't see a warning, you're fine.

\n

Remapping exit codes

\n

Tini will reuse the child's exit code when exiting, but occasionally, this may
\nnot be exactly what you want (e.g. if your child exits with 143 after receiving
\nSIGTERM). Notably, this can be an issue with Java apps.

\n

In this case, you can use the -e flag to remap an arbitrary exit code to 0.
\nYou can pass the flag multiple times if needed.

\n

For example:

\n
tini -e 143 -- ...\n
\n

Process group killing

\n

By default, Tini only kills its immediate child process. This can be
\ninconvenient if sending a signal to that process does not have the desired
\neffect. For example, if you do

\n
docker run --rm krallin/ubuntu-tini sh -c 'sleep 10'\n
\n

and ctrl-C it, nothing happens: SIGINT is sent to the 'sh' process,
\nbut that shell won't react to it while it is waiting for the 'sleep'
\nto finish.

\n

You can configure Tini to kill the child process group, so that every process
\nin the group gets the signal, by either:

\n\n

This corresponds more closely to what happens when you do ctrl-C etc. in a
\nterminal: The signal is sent to the foreground process group.

\n
docker run --rm --entrypoint tini krallin/ubuntu-tini -g -- sh -c 'sleep 10'\n
\n

Parent Death Signal

\n

Tini can set its parent death signal, which is the signal Tini should receive
\nwhen its parent exits. To set the parent death signal, use the -p flag with
\nthe name of the signal Tini should receive when its parent exits:

\n
tini -p SIGTERM -- ...\n
\n

NOTE: See this PR discussion to learn more about the parent death signal
\nand use cases.

\n

More

\n

Existing Entrypoint

\n

Tini can also be used with an existing entrypoint in your container!

\n

Assuming your entrypoint was /docker-entrypoint.sh, then you would use:

\n
ENTRYPOINT [\"/tini\", \"--\", \"/docker-entrypoint.sh\"]\n
\n

Statically-Linked Version

\n

Tini has very few dependencies (it only depends on libc), but if your
\ncontainer fails to start, you might want to consider using the statically-built
\nversion instead:

\n
ADD https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini-static /tini\n
\n

Size Considerations

\n

Tini is a very small file (in the 10KB range), so it doesn't add much weight
\nto your container.

\n

The statically-linked version is bigger, but still < 1M.

\n

Building Tini

\n

If you'd rather not download the binary, you can build Tini by running
\ncmake . && make.

\n

Before building, you probably also want to run:

\n
export CFLAGS=\"-DPR_SET_CHILD_SUBREAPER=36 -DPR_GET_CHILD_SUBREAPER=37\"\n
\n

This ensure that even if you're building on a system that has old Linux Kernel
\nheaders (< 3.4), Tini will be built with child subreaper support. This is
\nusually what you want if you're going to use Tini with Docker (if your host
\nKernel supports Docker, it should also support child subreapers).

\n

Understanding Tini

\n

After spawning your process, Tini will wait for signals and forward those
\nto the child process, and periodically reap zombie processes that may be
\ncreated within your container.

\n

When the \"first\" child process exits (/your/program in the examples above),
\nTini exits as well, with the exit code of the child process (so you can
\ncheck your container's exit code to know whether the child exited
\nsuccessfully).

\n

Debugging

\n

If something isn't working just like you expect, consider increasing the
\nverbosity level (up to 3):

\n
tini -v    -- bash -c 'exit 1'\ntini -vv   -- true\ntini -vvv  -- pwd\n
\n

Authors

\n

Maintainer:

\n\n

Contributors:

\n\n

Special thanks to:

\n","updatedAt":"2025-05-22T01:50:59Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"Docker-Tools","color":"abbcfb"}},{"node":{"name":"krallin","color":"c64af5"}}]},"comments":{"edges":[]}}},"pageContext":{"number":564,"previous":{"title":"fantasticit/think: 一款开源知识管理工具，通过独立的知识库空间，结构化地组织在线协作文档，实现知识的积累与沉淀，促进知识的复用与流通","number":563},"next":{"title":"tiny-craft/tiny-rdm: 一款现代轻量级跨平台 Redis 桌面管理器，适用于 Mac、Windows 和 Linux。颜值高，功能丰富。","number":565}}}, "staticQueryHashes": ["151096407","2861350382"]}