From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: Kilian Zinnecker <kilian.zinnecker@mail.de>, yann.morin.1998@free.fr
Subject: Re: [Buildroot] Buildroot docker image
Date: Sat, 2 Sep 2023 09:42:44 +0200 [thread overview]
Message-ID: <20230902094244.0251e004@windsurf> (raw)
In-Reply-To: <7af21f66-d3c5-e42f-03e5-8a1f6b370520@mind.be>
On Fri, 1 Sep 2023 09:19:02 +0200
Arnout Vandecappelle via buildroot <buildroot@buildroot.org> wrote:
> First of all, the one on dockerhub is no longer updated. The images we
> actually use are on registry.gitlab.com/buildroot.org/buildroot/base
>
> But even those images are not really "for user consumption". They are the
> images we use for CI, and they therefore have a bit more stuff in them than
> really needed, e.g. qemu. They are also not updated (on the OS level) - no
> security updates or anything are applied on it.
>
> It would probably be better if we would also create a small image that people
> can use for just building in their CI. A small image based on e.g. Alpine or
> Arch, and that is updated e.g. daily on dockerhub. However, nobody ever
> contributed such an image so we don't have it.
Yann has been working on and off on a set of Docker images for
Buildroot. See his branch at
https://gitlab.com/ymorin/buildroot/-/commits/yem/dockers/. I indeed
shared with him recently on IRC that it would be nice to have a really
minimal image, separate from the image used in CI (which has more stuff
enabled, most notably python3).
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-02 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 6:51 [Buildroot] Buildroot docker image Kilian Zinnecker via buildroot
2023-09-01 7:19 ` Arnout Vandecappelle via buildroot
2023-09-02 7:42 ` Thomas Petazzoni via buildroot [this message]
2023-12-03 11:47 ` Kilian Zinnecker via buildroot
2023-12-09 21:29 ` Arnout Vandecappelle via buildroot
2023-12-10 12:17 ` Thomas Petazzoni via buildroot
2023-12-10 19:28 ` Peter Korsgaard
2023-12-10 13:48 ` Yann E. MORIN
2023-12-10 13:51 ` Yann E. MORIN
2023-12-10 17:02 ` Thomas Petazzoni via buildroot
2023-12-10 18:46 ` Yann E. MORIN
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=20230902094244.0251e004@windsurf \
--to=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.