-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't boot on some platforms, need way to modify initramfs contents #180
Comments
I started with a |
I think we should finish the work here. The current
|
Yes, totally agree. Will put it to the top of my list. |
This is the ami generated on Travis if anyone needs it: |
Done with #194 |
Some platforms (notably Azure) require that the initramfs contains certain binaries, modules, or kernel drivers in order to boot properly.
This means osbuild needs a way to modify the contents of the image's current initramfs (if it has one), and to make those configuration changes persistent so any future initramfs built inside the image (e.g. on a future kernel update) will also contain the needed pieces.
lorax-composer
and other tools handle this by creating files in/etc/dracut.conf.d/
in kickstart%post
scriptlets - seevhd.ks
for an example.The best way for osbuild to handle this is probably to have a stage that allows creating dracut config files and building new initrd images for any/all kernel(s) present in the tree.
For feature parity with
lorax-composer
and current official RHEL images, this stage needs to support at least the following dracut.conf(5) options:add_drivers
add_dracutmodules
install_items
dracut_rescue_image
(most image types remove the rescue image to save space)early_microcode
(on by default but some image types turn it off)omit_dracutmodules
(e.g.live-img
removesplymouth
)After modifying the dracut config, the initrd images have to be (re)generated by (re)running dracut. See
pylorax.treebuilder.rebuild_initrds()
andpylorax.creator.rebuild_initrds_for_live()
for details on howlorax-composer
handles finding the correct kernel version, output filename, etc.The text was updated successfully, but these errors were encountered: