From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Kilian Zinnecker <kilian.zinnecker@mail.de>,
Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Buildroot docker image
Date: Sun, 10 Dec 2023 14:51:41 +0100 [thread overview]
Message-ID: <ZXXCbVmFjaGlzOVT@landeda> (raw)
In-Reply-To: <ZXXBnuTeg_LcSWgZ@landeda>
Re.
On 2023-12-10 14:48 +0100, Yann E. MORIN spake thusly:
> Thomas, All,
>
> On 2023-09-02 09:42 +0200, Thomas Petazzoni via buildroot spake thusly:
> > 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).
>
> I was looking at this right now, and in fact I believe the existing
> image is the perfect fir as the minimal image to use.
s/fir/fit/
> Indeed, let's take a look at what we have there, and why we do:
>
> MTSCR
> × bc
> × build-essential
> bzr
> × ca-certificates
> × cmake
cmake should have been in the 'S' column.
Regards,
Yann E. MORIN.
> × cpio
> × cvs
> × file
> × g++-multilib
> × git
> × libc6:i386
> × libncurses5-dev
> × locales
> mercurial
> × openssh-server
> ×× python3
> × python3-flake8
> × python3-magic
> × python3-nose2
> × python3-pexpect
> × python3-pytest
> × qemu-system-arm
> × qemu-system-misc
> × qemu-system-x86
> × rsync
> × shellcheck
> subversion
> × unzip
> × wget
>
> M: strictly mandatory
> T: optional, but helps use pre-built toolchains
> S: optional, speeds up the build
> C: needed to run check-package et al.
> R: needed to run the runtime test-suite
>
> Bazaar, mercurial and subversion are optional, and only required when a
> package is bzr-, hg-, or svn-hosted, but if we want this image to be
> usable generally, it should have all three.
>
> Since mercurial is a python package, we can't drop python3, and the
> remaining modules are relatively small in comparison to the rest.
>
> Getting a more minimal image would be just about dropping qemu. That
> would make for an image that we could not use in the CI, and that would
> not be usable to test the changes done to Buildroot. I don't think that
> would mkae for a good image.
>
> The size of this image is currently ~330MiB to download, and ~975MiB of
> storage; building an image without qemu would not make much of a
> difference.
>
> So, I think this is the best minimal we can get to, as it contains
> everything that people should need to build and to run the tooling.
>
> Regards,
> Yann E. MORIN.
>
> --
> .-----------------.--------------------.------------------.--------------------.
> | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
> | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
> '------------------------------^-------^------------------^--------------------'
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-12-10 13:51 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
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 [this message]
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=ZXXCbVmFjaGlzOVT@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
--cc=thomas.petazzoni@bootlin.com \
/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