All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/9] docker-engine: add support for init processes
Date: Fri, 22 Sep 2017 00:09:40 +0100	[thread overview]
Message-ID: <CA+h8R2pkz7=vpzbScAShZrdZU3=QDoKoPc7+iwVVP4vBiX=4JQ@mail.gmail.com> (raw)
In-Reply-To: <859c9ec7-7a17-cfef-ac9f-8982d8f8c086@mind.be>

Hi Arnout,

I marked this series as RFC on patchwork, just because there are a
couple of fixes I have applied and will respin after people are done
reviewing.

On Thu, Sep 21, 2017 at 10:37 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
>  On my Debian system there is no docker-init but I don't get this warning when
> starting docker...

This is likely because Docker has changed since I wrote this patch
originally, which was against a version 4 versions ago around 6 months
ago.

>  Upstream URL is not needed here, only in the package itself.

Interesting, I put it there because for some reason I remember seeing
the upstream URL in the Config.in for other packages. Will remove.

>  It might be useful to add some help text that indicates the difference between
> tini and dumb-init.

Functionally there is none, but the actual implementations are just
slightly different by different authors. Tini is a bit newer but
backed by a less trusted source while dumb-init is old and backed by
Yelp. For some reason Tini is used by the docker official
distribution.

Best,
Christian

  reply	other threads:[~2017-09-21 23:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20  3:02 [Buildroot] [PATCH 0/9] Upgrading Go to 1.9 and Docker to v2017.07 Christian Stewart
2017-09-20  3:02 ` [Buildroot] [PATCH 1/9] dumb-init: new package Christian Stewart
2017-09-21 21:23   ` Arnout Vandecappelle
2017-09-21 23:13     ` Christian Stewart
2017-09-20  3:02 ` [Buildroot] [PATCH 2/9] tini: " Christian Stewart
2017-09-20  4:40   ` Baruch Siach
2017-09-20 10:32     ` Christian Stewart
2017-09-20  3:02 ` [Buildroot] [PATCH 3/9] docker-engine: add support for init processes Christian Stewart
2017-09-21 21:37   ` Arnout Vandecappelle
2017-09-21 23:09     ` Christian Stewart [this message]
2017-09-20  3:02 ` [Buildroot] [PATCH 4/9] docker-engine: select static for tini and dumb-init Christian Stewart
2017-09-20  3:02 ` [Buildroot] [PATCH 5/9] docker-proxy: new package Christian Stewart
2017-09-20  3:02 ` [Buildroot] [PATCH 6/9] docker-engine: add dependency on docker-proxy Christian Stewart
2017-09-20  3:02 ` [Buildroot] [PATCH 7/9] runc: bump to v1.0.0-rc4 Christian Stewart
2017-09-20  3:02 ` [Buildroot] [PATCH 8/9] docker-containerd: bump to 3addd84 Christian Stewart
2017-09-20  3:02 ` [Buildroot] [PATCH 9/9] docker-engine: bump to v17.07.0-ce Christian Stewart

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='CA+h8R2pkz7=vpzbScAShZrdZU3=QDoKoPc7+iwVVP4vBiX=4JQ@mail.gmail.com' \
    --to=christian@paral.in \
    --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.