| Message ID | 20240510030937.3789910-1-johannes.schneider@leica-geosystems.com |
|---|---|
| Headers | show |
| Series | pkg-database and systemd-sysext image | expand |
Hello,
This still fails on the autobuilders, I'm pretty sure the config for the
build folder has:
PACKAGE_CLASSES = "package_rpm"
This explains this:
build-st-4166614$ tree tmp/deploy/images/qemux86-64/var/lib/
tmp/deploy/images/qemux86-64/var/lib/
├── dnf
│ ├── history.sqlite
│ ├── history.sqlite-shm
│ └── history.sqlite-wal
└── rpm
├── rpmdb.sqlite
├── rpmdb.sqlite-shm
└── rpmdb.sqlite-wal
3 directories, 6 files
Are you testing with plain poky?
On 10/05/2024 05:09:34+0200, Johannes Schneider wrote:
> 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:
> tests: restructure to call 'bitbake' only once in the testcase itself
> (in hopes of solving the autobuilder problem; local test runs succeed)
>
> changes with v7:
> tests: undo the restructuring of done in v6, in favour of explicitly forcing steps:
> '-c rootfs -f'. since concurrency of the autobuilder, and reusing artifacts/sstate-caching is probably the issue?
Hoi > > This still fails on the autobuilders, I'm pretty sure the config for the > build folder has: > PACKAGE_CLASSES = "package_rpm" > aha! that is the missing puzzle piece - thanks! thought i read somewhere that ipk is the default and geared the tests towards that... "always check yous assumptions" > > This explains this: > > build-st-4166614$ tree tmp/deploy/images/qemux86-64/var/lib/ > tmp/deploy/images/qemux86-64/var/lib/ > ├── dnf > │ ├── history.sqlite > │ ├── history.sqlite-shm > │ └── history.sqlite-wal > └── rpm > ├── rpmdb.sqlite > ├── rpmdb.sqlite-shm > └── rpmdb.sqlite-wal > > 3 directories, 6 files > ...which make me realize that there needs to be a test for all three packagemanagers; at least on the "gen_pkgdb_fs" side -> expect a v8 > > Are you testing with plain poky? > yes, i've checked out just the 'openembeddec-core' plus 'bitbake' layers; and run the tests "vanilla" on that setup - which default to using 'package_ipk' = no wonder my local test runs always succeeded :-D feature request for the autobuilder logs: include a config dump at the beginning? (or a link to the config git repo + sha; or the docs?) gruß Johannes
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: tests: restructure to call 'bitbake' only once in the testcase itself (in hopes of solving the autobuilder problem; local test runs succeed) changes with v7: tests: undo the restructuring of done in v6, in favour of explicitly forcing steps: '-c rootfs -f'. since concurrency of the autobuilder, and reusing artifacts/sstate-caching is probably the issue?