From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: Kilian Zinnecker <kilian.zinnecker@mail.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
yann.morin.1998@free.fr
Subject: Re: [Buildroot] Buildroot docker image
Date: Sun, 10 Dec 2023 20:28:20 +0100 [thread overview]
Message-ID: <87msuhoo17.fsf@48ers.dk> (raw)
In-Reply-To: <a6f09f61-573b-465a-b5a9-6d175c313f2b@mind.be> (Arnout Vandecappelle via buildroot's message of "Sat, 9 Dec 2023 22:29:32 +0100")
>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot@buildroot.org> writes:
Hi,
> In retrospect, this was probably a mistake :-) Alpine is based on the
> musl libc, and as you noticed below, there are host tools that don't
> work with musl. Clearly, nobody is using Buildroot on a musl-based
> build machine at the moment, since nobody ever complained about this
> (and fakeroot always needs to be built).
Yes, lets stick to a "normal" glibc based distribution.
> So, if we do go for Alpine as the official docker image, we can
> expect quite a lot of breakage... Therefore, before going there, I
> think we should go for a "normal" distro after all for the time
> being. Of all the traditional distros, ubuntu:22.04 has by far the
> smallest image at 80MB (this actually came as quite the surprise to
> me... I have no idea why Fedora would be twice as large! But it does
> already include Python, so after installing all necessary packages it
> may even out again...).
I think Fedora is the outlier here, Debian is similar to Ubuntu:
docker image ls debian:12.2\*
REPOSITORY TAG IMAGE ID CREATED SIZE
debian 12.2-slim 31d5e503c34f 2 weeks ago 74.8MB
debian 12.2 0ce03c8a15ec 2 weeks ago 117MB
Given that we already use Debian for the "CI" container, it IMHO makes
sense to use it here as well.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-12-10 19:28 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 [this message]
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=87msuhoo17.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox