From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Sat, 11 Aug 2018 00:17:20 +0200 Subject: [Buildroot] [PATCH v1 1/1] tini: new package In-Reply-To: References: <20180810184255.17612-1-christian@paral.in> <20180810215502.1647fe01@windsurf> Message-ID: <20180811001720.6f407992@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Fri, 10 Aug 2018 15:11:11 -0700, Christian Stewart wrote: > On Fri, Aug 10, 2018 at 12:55 PM Thomas Petazzoni > 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 ? > 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 ? Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com