All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/1] tini: new package
Date: Sat, 11 Aug 2018 00:17:20 +0200	[thread overview]
Message-ID: <20180811001720.6f407992@windsurf> (raw)
In-Reply-To: <CA+h8R2pEc4A-=jch5c1A8SchJv6K+LZrrHSy+EcSbp=Tnw6Xvg@mail.gmail.com>

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@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 ?

> 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

  reply	other threads:[~2018-08-10 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 18:42 [Buildroot] [PATCH v1 1/1] tini: new package Christian Stewart
2018-08-10 19:55 ` Thomas Petazzoni
2018-08-10 22:11   ` Christian Stewart
2018-08-10 22:17     ` Thomas Petazzoni [this message]
2018-08-10 23:33       ` Matthew Weber
2018-08-14 13:57 ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180811001720.6f407992@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.