From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/testing: add docker / docker-compose tests
Date: Mon, 4 Feb 2019 19:53:45 +0100 [thread overview]
Message-ID: <20190204195345.6494760a@windsurf> (raw)
In-Reply-To: <20190204165557.2160-1-peter@korsgaard.com>
On Mon, 4 Feb 2019 17:55:57 +0100
Peter Korsgaard <peter@korsgaard.com> 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.
Do you need to duplicate the kernel config entirely, or can you use
board/qemu/x86_64/linux.config + a fragment ?
> Docker needs entropy at startup, so enable the virtio-rng-pci device to
> expose entropy to the guest. The default RAM amount (128M) is not enough to
> run docker / docker-compose, so bump to 512MB.
Wow. Go is efficient :)
> diff --git a/support/testing/conf/docker-compose.yml b/support/testing/conf/docker-compose.yml
> new file mode 100644
> index 0000000000..49ff2677da
> --- /dev/null
> +++ b/support/testing/conf/docker-compose.yml
> @@ -0,0 +1,4 @@
> +version: '3'
> +services:
> + busybox:
> + image: "busybox:latest"
Is conf/ really the right place for this ? Don't we have some other
place to store the per-tests artifacts that go on the target ? I don't
think we have a good organization for this at the moment, so this will
do for now.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-04 18:53 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
2019-02-05 9:13 ` Peter Korsgaard
2019-02-04 18:53 ` Thomas Petazzoni [this message]
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=20190204195345.6494760a@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.