From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/testing: add docker / docker-compose tests
Date: Tue, 05 Feb 2019 10:18:02 +0100 [thread overview]
Message-ID: <87sgx2pp9x.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <5c58db4159d1d_290e2ab5f55cf3201186d@ultri5.mail> (ricardo martincoski's message of "Mon, 04 Feb 2019 22:39:29 -0200")
>>>>> "ricardo" == ricardo martincoski <ricardo.martincoski@gmail.com> writes:
> Hello,
> On Mon, Feb 04, 2019 at 03:11 PM, Matthew Weber wrote:
>> On Mon, Feb 4, 2019 at 10:56 AM Peter Korsgaard wrote:
>>>
>>> Build for x86-64 as public containers in general are only available for
>>> x86-64. Docker needs a number of kernel options enabled, so use a custom
>>> kernel config based on the qemu one.
>>>
>>> Docker needs entropy at startup, so enable the virtio-rng-pci device to
>>> expose entropy to the guest.
>>
>> Another option is enabling BR2_PACKAGE_HAVEGED to let the target compensate.
> This is already used for 2 python test cases (pynacl and crossbar).
> I don't have specific knowledge to say which is the best approach. For the
> python test cases I just searched for *any* way to have enough entropy.
I don't think it is really clear cut. Haveged is probably not something
you should be using on a real system, and it only starts up relatively
late so there could be issues with early user space (E.G. I have had
issues with running mkfs.ext4 very early), but the virtio-rng-pci device
is only available for a limited set of qemu targets (E.G. the ones that
emulate a PCI bus).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-02-05 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 16:55 [Buildroot] [PATCH] support/testing: add docker / docker-compose tests Peter Korsgaard
2019-02-04 17:11 ` Matthew Weber
2019-02-05 0:39 ` ricardo.martincoski at gmail.com
2019-02-05 9:18 ` Peter Korsgaard [this message]
2019-02-05 9:13 ` Peter Korsgaard
2019-02-04 18:53 ` Thomas Petazzoni
2019-02-04 20:20 ` Peter Korsgaard
2019-02-05 0:47 ` Ricardo Martincoski
2019-02-05 22:05 ` Peter Korsgaard
2019-02-05 22:08 ` Matthew Weber
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=87sgx2pp9x.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox