From: Johannes Schneider <johannes.schneider@leica-geosystems.com>
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org, alex.kanavin@gmail.com,
alexandre.belloni@bootlin.com
Cc: Johannes Schneider <johannes.schneider@leica-geosystems.com>
Subject: [PATCH v6 0/3] pkg-database and systemd-sysext image
Date: Mon, 15 Apr 2024 08:02:00 +0200 [thread overview]
Message-ID: <20240415060203.2961-1-johannes.schneider@leica-geosystems.com> (raw)
systemd-sysext allows to overlay another image (or multiple) ontop of
a "base-image" = the current rootfs, via the use of overlayfs; to add
tools and features meant for development purposes.
To quote the documentation on systemd-sysext:
" ...addition in order to make debugging/development easier). System
extension images should not be misunderstood as a generic software
packaging framework, ..."
To build a lean image, that only holds packages that are not already
part of the base-image, a snapshot of the package-database is taken
after the installation of the base-rootfs is done, and picked up again
when collecting the rootfs of such a extension image.
with all this in place an example usage could look like this:
some-core-image.bb
inherit core-image
IMAGE_GEN_PKGDBFS = "1"
extending-image.bb
inherit image-sysext
IMAGE_FSTYPES = "squashfs"
IMAGE_BASE_PKGDB = "some-core-image"
# the above pointing at a package-db similar to:
# build/deploy/images/$MACHINE/some-core-image-$MACHINE-20240210172305-pkgdb.rootfs.tar.gz
then on the device, running some-core-image, with the extension image placed at FN:
$> ln -s "$FN" /run/extensions/$(basename $FN).raw
$> systemd-sysext list
$> SYSTEMD_LOG_LEVEL=debug systemd-sysext merge
As long as the VERSION_ID of the extension image matches the os-release
in the base image, the above commands return sucessfully;
for details on the compativility check see the docs for systemd-sysext.
=========
changes with v2:
rebase from 'kirkstone' onto 'master'
changes with v3:
incorporate review suggestions for simplification
add task dependency handling
add oe-selftest for the pkgdb handling
add variable documentation and
some more comments, and examples in the commit-msg
changes with v4:
rebase onto 'master' => no functional changes
fixed patchtest findings
changes with v5:
rebase onto 'master'
add '.sysext' to the deployed symlink name
sidenote on the tests and autobuilder failure: run locally they succeed, e.g.:
#> oe-selftest --verbose -r imagefeatures.ImageFeatures.test_image_gen_pkgdbfs
changes with v6:
restructure test to call 'bitbake' only once in the testcase itself
(in hopes of solving the autobuilder problem; local test runs succeed)
next reply other threads:[~2024-04-15 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 6:02 Johannes Schneider [this message]
2024-04-15 6:02 ` [PATCH v6 1/3] image.bbclass/rootfs: archive and deploy package database Johannes Schneider
2024-04-15 6:02 ` [PATCH v6 2/3] image.bbclass/rootfs: set and unpack package-database Johannes Schneider
2024-04-15 6:02 ` [PATCH v6 3/3] classes: add a systemd-sysext image class Johannes Schneider
2024-04-21 20:36 ` [OE-core] [PATCH v6 0/3] pkg-database and systemd-sysext image Alexandre Belloni
2024-04-22 4:16 ` SCHNEIDER Johannes
2024-05-10 3:09 Johannes Schneider
2024-05-11 23:07 ` Alexandre Belloni
2024-05-12 5:56 ` SCHNEIDER Johannes
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=20240415060203.2961-1-johannes.schneider@leica-geosystems.com \
--to=johannes.schneider@leica-geosystems.com \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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;
as well as URLs for NNTP newsgroup(s).