From: eric.smith@oss.qualcomm.com
To: openembedded-devel@lists.openembedded.org
Subject: Using dracut to create an initramfs image via bitbake
Date: Tue, 10 Jun 2025 17:52:24 -0700 [thread overview]
Message-ID: <1pXS.1749603144841364915.mHTW@lists.openembedded.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
Hello OpenEmbedded developers,
I am curious if there's been discussion on trying to use dracut to build an initramfs image via bitbake. To be clear, I mean running dracut on the build host machine from a bitbake recipe, and having this dracut use files from the target image rootfs to build the initramfs.
Right now in meta-openembedded/meta-initramfs/recipes-devtools it looks like there's a dracut recipe to build dracut for the target arch, but no native dracut recipe. So with the current dracut recipe, this dracut can only be used from an architecture matching the target arch. This is not cross-compatible.
There has been a recent improvement in dracut to enable a native dracut to work with cross-compiled binaries. See the merged patch that should go into the next major dracut version 107 which replaces dracut's ldd usage - Parse ELF .note.dlopen entries for dependencies, replace ldd for better cross support by chewi · Pull Request #1260 · dracut-ng/dracut-ng · GitHub ( https://github.com/dracut-ng/dracut-ng/pull/1260 )
If there's no active development on using the latest dracut to build an initramfs, I'd like to work on it. Specifically I want to create a dracut native recipe and a dracut initramfs test image that uses the native dracut and a machine image's rootfs to create an initramfs. I understand this work would be dependent on a newer dracut that's not released yet.
What would be the testing expectations that I should run for my patches? Run testimage, as documented in the following? 4 Contributing Changes to a Component — The Yocto Project ® 5.2.999 documentation ( https://docs.yoctoproject.org/contributor-guide/submit-changes.html#test-your-changes )
Thank you,
Eric
[-- Attachment #2: Type: text/html, Size: 1964 bytes --]
next reply other threads:[~2025-06-11 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 0:52 eric.smith [this message]
2025-06-11 8:37 ` [oe] Using dracut to create an initramfs image via bitbake Alexander Kanavin
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=1pXS.1749603144841364915.mHTW@lists.openembedded.org \
--to=eric.smith@oss.qualcomm.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.