From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Hombourger, Cedric" <cedric.hombourger@siemens.com>
Subject: Re: [RFC 1/2] rootfs: download packages with host apt
Date: Tue, 21 Jul 2026 15:02:04 +0000 [thread overview]
Message-ID: <5da1e31182c28648a188de3146e71131e7878b6d.camel@siemens.com> (raw)
In-Reply-To: <9a53f70e-f23a-4a49-885c-da3177efed11@ilbers.de>
On Tue, 2026-07-21 at 16:56 +0300, Anton Mikanovich wrote:
> Hello Felix,
>
> 20.07.2026 13:52, 'Felix Moessbauer' via isar-users wrote:
> > The dependency resolving and download are architecture unspecific, hence
> > they do not need to be emulated. By not emulating them, we follow the
> > approach of mmdebstrap and significantly speedup this operation.
> >
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> > meta/classes-recipe/rootfs.bbclass | 40 ++++++++++++++----------------
> > 1 file changed, 19 insertions(+), 21 deletions(-)
> >
> > diff --git a/meta/classes-recipe/rootfs.bbclass b/meta/classes-recipe/rootfs.bbclass
> > index e17f711f..6af29b40 100644
> > --- a/meta/classes-recipe/rootfs.bbclass
> > +++ b/meta/classes-recipe/rootfs.bbclass
> > @@ -337,10 +337,12 @@ rootfs_install_pkgs_download[progress] = "custom:rootfs_progress.PkgsDownloadPro
> > rootfs_install_pkgs_download[isar-apt-lock] = "release-after"
> > rootfs_install_pkgs_download[network] = "${TASK_USE_NETWORK}"
> > rootfs_install_pkgs_download() {
> > - # download packages using apt in a non-privileged namespace
> > - rootfs_cmd --bind "${ROOTFSDIR}/var/cache/apt/archives" /var/cache/apt/archives \
> > - ${ROOTFSDIR} \
> > - -- /usr/bin/apt-get ${ROOTFS_APT_ARGS} -o Debug::NoLocking=1 --download-only ${ROOTFS_PACKAGES}
> > + # download packages using the host apt in a non-privileged namespace.
> > + rootfs_cmd --bind "${ROOTFSDIR}" "${ROOTFSDIR}" \
> > + -- /usr/bin/apt-get -o APT::Architecture=${ROOTFS_ARCH} \
> > + -o Dir="${ROOTFSDIR}" \
> > + ${ROOTFS_APT_ARGS} -o Debug::NoLocking=1 \
> > + --download-only ${ROOTFS_PACKAGES}
> Why do we need rootfs_cmd API usage then?
> Doesn't it actually still use apt-get from ROOTFSDIR?
We at least need it to bind-mount /isar-apt and /dev, ... on unshare.
But you're right, the /bin, /etc, /lib, ... mounts look scary.
Maybe Cedric can help to get the implementation right.
I just sent this as an RFC, as I want to get feedback about the general
approach to use the host apt for more things (we are anyways already
doing this via mmdebstrap).
> > }
> >
> > ROOTFS_INSTALL_COMMAND_BEFORE_EXPORT ??= ""
> > @@ -356,23 +358,19 @@ ROOTFS_INSTALL_COMMAND += "rootfs_install_pkgs_isar_download"
> > rootfs_install_pkgs_isar_download[weight] = "50"
> > rootfs_install_pkgs_isar_download[isar-apt-lock] = "acquire-before release-after"
> > rootfs_install_pkgs_isar_download() {
> > - mkdir -p "${WORKDIR}/dpkg"
> > -
> > - # Use our own dpkg lock files rather than those in the rootfs since we are not root
> > - # (this is safe as there are no concurrent apt/dpkg operations for that rootfs)
> > - touch "${WORKDIR}/dpkg/lock" "${WORKDIR}/dpkg/lock-frontend"
> > -
> > - # Command apt-get install do not cache packages from local repos
> > - # We can obtain non cached package URIs by recalling install command here
> > - # No need in export those files to dl_dir, so we can run it right after
> > - rootfs_cmd --bind "${ROOTFSDIR}/var/cache/apt/archives" /var/cache/apt/archives \
> > - --bind "${WORKDIR}/dpkg/lock" /var/lib/dpkg/lock \
> > - --bind "${WORKDIR}/dpkg/lock-frontend" /var/lib/dpkg/lock-frontend \
> > - --chdir "/var/cache/apt/archives" \
> > - ${ROOTFSDIR} \
> > - -- /usr/bin/sh -c "apt-get ${ROOTFS_APT_ARGS} --print-uris ${ROOTFS_PACKAGES} | \
> > - sed -n \"s|^.*/\\(.*\\)_[^_]*_[^_]*\\.deb'.*|\\1|p\" | \
> > - xargs -r apt-get download"
> > + # apt-get install does not cache packages coming from local repos
> > + # (isar-apt). Obtain their URIs by recalling the install command and
> > + # download them using the host apt, same as rootfs_install_pkgs_download.
> > + # No need to export those files to dl_dir, so we can run it right after.
> > + rootfs_cmd --bind "${ROOTFSDIR}" "${ROOTFSDIR}" \
> > + --chdir "${ROOTFSDIR}/var/cache/apt/archives" \
> > + -- /usr/bin/sh -c "apt-get -o APT::Architecture=${ROOTFS_ARCH} \
> > + -o \"Dir=${ROOTFSDIR}\" -o Debug::NoLocking=1 \
> > + ${ROOTFS_APT_ARGS} --print-uris ${ROOTFS_PACKAGES} | \
> > + sed -n \"s|^.*/\\(.*\\)_[^_]*_[^_]*\\.deb'.*|\\1|p\" | \
> > + xargs -r apt-get -o APT::Architecture=${ROOTFS_ARCH} \
> > + -o \"Dir=${ROOTFSDIR}\" -o Debug::NoLocking=1 \
> > + download"
> Besides of the same question, this task rebuild will probably also helps
> with
> ignoring missing deb file arch in the existing implementation, which can
> possibly fail if we try to build custom package for both host and target
> architectures.
Probably, because we are explicit. But I don't know of any bugs we
currently have regarding this.
Felix
> > }
> >
> > ROOTFS_INSTALL_COMMAND += "${@ 'rootfs_install_clean_files' if (d.getVar('ROOTFS_CLEAN_FILES') or '').strip() else ''}"
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/5da1e31182c28648a188de3146e71131e7878b6d.camel%40siemens.com.
prev parent reply other threads:[~2026-07-21 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 10:52 'Felix Moessbauer' via isar-users
2026-07-20 10:52 ` [RFC 2/2] rootfs: use host apt when installing in cross mode 'Felix Moessbauer' via isar-users
2026-07-21 13:58 ` Anton Mikanovich
2026-07-21 13:56 ` [RFC 1/2] rootfs: download packages with host apt Anton Mikanovich
2026-07-21 15:02 ` 'MOESSBAUER, Felix' via isar-users [this message]
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=5da1e31182c28648a188de3146e71131e7878b6d.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@siemens.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