[Buildroot] [PATCH v1 1/1] tini: new package

Matthew Weber matthew.weber at rockwellcollins.com
Fri Aug 10 23:33:31 UTC 2018


Thomas,
On Fri, Aug 10, 2018 at 5:17 PM Thomas Petazzoni
<thomas.petazzoni at bootlin.com> wrote:
>
> Hello,
>
> On Fri, 10 Aug 2018 15:11:11 -0700, Christian Stewart wrote:
>
> > On Fri, Aug 10, 2018 at 12:55 PM Thomas Petazzoni
> > <thomas.petazzoni at bootlin.com> wrote:
> > >
> > > What does "Docker now statically links to Tiny internally" mean ?
> >
> > I suppose the commit note is not clear. I am basically saying that we
> > do not need to statically link Tini, unlike previous revisions of this
> > commit. The intent of this package is no longer to satisfy the
> > docker-init requirement, but instead to just provide the "tini" binary
> > in the target environment, dynamically linked or otherwise.
>
> Why did the requirement change ?

Tini can be used for cases where you do a basic container and the
filesystem isn't isolated from the host.  Thus no need for static
building of the init process.

>
> > According to https://github.com/krallin/tini - NOTE: If you are using
> > Docker 1.13 or greater, Tini is included in Docker itself. This
> > includes all versions of Docker CE. To enable Tini, just pass the
> > --init flag to docker run.
>
> If Tini is included in Docker itself, why do we need a package for it ?

Basic LXC based containers can use it when are doing an abbreviated
init sequence for a container start.

Matt



More information about the buildroot mailing list