From: wenzong fan <wenzong.fan@windriver.com>
To: Seebs <seebs@seebs.net>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: pseudo 1.8.1 doesn't work with docker & dumb-init
Date: Wed, 7 Sep 2016 14:32:40 +0800 [thread overview]
Message-ID: <c4af9282-ed95-b7fc-f263-4a66eccfa4bf@windriver.com> (raw)
In-Reply-To: <BDCB4B3D-E034-4AFD-915C-8DDE5B66D76D@seebs.net>
On 09/02/2016 10:10 AM, Seebs wrote:
> On 1 Sep 2016, at 20:33, wenzong fan wrote:
>
>> No, I didn't think it's related to any specific docker version.
>>
>> I tested it on "Docker version 1.7.1, build 786b29d" & "Docker version
>> 1.11.2, build b9f10c9".
>>
>> BTW, I also tested the docker build w/o dumb-init, and the build works
>> ...
>
> Yeah, it's definitely specific in some way to docker.
>
> However, it doesn't appear to be 100% reproducible; I just tried a build
> with your reproducer and it completed without problems. (Unless the
> problems are more subtle, and don't prevent a build.) So this one's
> gonna be really fun to track down.
Yes, I believe it's not a 100 reproducible issue. Maybe you could run it
with other builds in parallel and try it 3 times or more.
It keeps high probability on my work host which a server that shared by
several persons, I can always get the error from 1 ~ 3 times build.
Thanks
Wenzong
>
> -s
next prev parent reply other threads:[~2016-09-07 6:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 9:21 pseudo 1.8.1 doesn't work with docker & dumb-init wenzong fan
2016-08-31 15:11 ` Joshua Lock
2016-09-02 1:24 ` wenzong fan
2016-08-31 15:48 ` Seebs
2016-09-02 1:33 ` wenzong fan
2016-09-02 2:10 ` Seebs
2016-09-07 6:32 ` wenzong fan [this message]
2016-09-07 6:40 ` Seebs
2016-09-14 20:46 ` Bystricky, Juro
2016-09-15 2:24 ` Randy MacLeod
2016-09-15 19:08 ` Randy MacLeod
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=c4af9282-ed95-b7fc-f263-4a66eccfa4bf@windriver.com \
--to=wenzong.fan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=seebs@seebs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox