From: Jan Kiszka <jan.kiszka@siemens.com>
To: Cedric Hombourger <cedric_hombourger@mentor.com>,
Helmut Grohne <helmut@subdivi.de>
Cc: isar-users <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@ilbers.de>,
"MacDonald, Joe" <Joe_MacDonald@mentor.com>
Subject: Re: [RFC] using lightweight containers instead of chroot
Date: Mon, 12 Jul 2021 16:35:20 +0200 [thread overview]
Message-ID: <5878a53d-7bf1-17c2-2b5b-ccf11460f405@siemens.com> (raw)
In-Reply-To: <b4c2dc7f-40b5-9581-fcd5-1bc08c9ddda5@mentor.com>
On 12.07.21 14:29, Cedric Hombourger wrote:
>
> On 7/12/2021 1:47 PM, Jan Kiszka wrote:
>> On 12.07.21 12:54, Helmut Grohne wrote:
>>> Hi Jan,
>>>
>>> On Mon, Jul 12, 2021 at 10:25:41AM +0200, Jan Kiszka wrote:
>>>> On 08.07.21 21:34, Helmut Grohne wrote:
>>>>> The reason to want DPKG_ROOT is to prepare the root filesystem for
>>>>> your
>>>>> embedded board. If that's not what you want to do, DPKG_ROOT is not
>>>>> your
>>>>> tool.
>>>> We want it for both the board and the build env. We have the same
>>>> issues
>>>> to solve there, means installing packages in unprivileged manner,
>>>> either
>>>> for target arch or the builder arch (cross and native builds need to be
>>>> supported). So I see DPKG_ROOT as a building block for both. In
>>>> addition, it would overcome qemu-user, which is speed gain.
>>> No. Let us for a moment assume that DPKG_ROOT would just work for all
>>> packages in Debian (and that is a far stretch really). Then you'd be
>>> able to install your Build-Depends into a directory without using
>>> chroot. But how do you build your package then? You need to chroot the
>>> dpkg-buildpackage call. So you are back to requiring chroot, at which
>>> point you can just install your whole build environment using chroot.
>>>
>>> DPKG_ROOT is the wrong tool for that job. The one thing that it fixes is
>>> requiring qemu for the embedded filesystem image. Cross builds already
>>> work entirely without qemu (including package installation).
>>>
>> We can't cross-build all packages, unfortunately. That's why we will
>> continue to require native installations for some packages'
>> buildchroots, just like we obviously do for the target rootfs. If you
>> can create and also augment (install deps) those without qemu, you gain
>> speed. Granted, those continue to require qemu for the actual build.
>> Which brings me back to still having to add namespace support to
>> binfmt_misc...
>
> there is that:
> https://patchwork.criu.org/series/3855/
>
>
> I haven't checked if the author got any luck in getting his patchset
> accepted
>
See https://lkml.org/lkml/2021/1/18/1267. Since then, it's on my long
backlog, but with rather low prio unfortunately.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-07-12 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 9:07 Cedric Hombourger
2021-07-08 11:38 ` Jan Kiszka
2021-07-08 13:52 ` Helmut Grohne
2021-07-08 17:16 ` Jan Kiszka
2021-07-08 19:34 ` Helmut Grohne
2021-07-12 8:25 ` Jan Kiszka
2021-07-12 10:54 ` Helmut Grohne
2021-07-12 11:47 ` Jan Kiszka
2021-07-12 12:29 ` Cedric Hombourger
2021-07-12 14:35 ` Jan Kiszka [this message]
2021-07-09 15:46 ` Cedric Hombourger
2021-07-09 16:12 ` Cedric Hombourger
2021-07-26 13:55 ` Anton Mikanovich
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=5878a53d-7bf1-17c2-2b5b-ccf11460f405@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Joe_MacDonald@mentor.com \
--cc=cedric_hombourger@mentor.com \
--cc=helmut@subdivi.de \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.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