containers/bootc
1
0
Fork 0
mirror of https://github.com/containers/bootc.git synced 2026-02-05 15:45:53 +01:00
Code Issues Activity

docs: Add bootloaders.md

Browse Source 
This one is important.

Signed-off-by: Colin Walters <walters@verbum.org>
This commit is contained in:
Colin Walters
2025-06-05 13:06:14 -04:00
parent 4674678bed
commit 88a830a5af
2 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/src/SUMMARY.md
View File

@@ -51,6 +51,7 @@
- [Filesystem](filesystem.md)
- [Filesystem: sysroot](filesystem-sysroot.md)
- [Container storage](filesystem-storage.md)
- [Bootloader](bootloader.md)
# Experimental features

9
docs/src/bootloaders.md Normal file
View File

@@ -0,0 +1,9 @@
# Bootloaders in `bootc`
`bootc` uses [bootupd](https://github.com/coreos/bootupd/) by default to manage bootloader installation and configuration. `bootupd` is an external project that abstracts over bootloader installs and upgrades, providing a consistent interface for different bootloader types (e.g., GRUB, systemd-boot).
When you run `bootc install`, it invokes `bootupctl backend install` to install the bootloader to the target disk or filesystem. The specific bootloader configuration is determined by the container image and the target system's hardware.
Currently, `bootc` only runs `bootupd` during the installation process. It does **not** automatically run `bootupctl update` to update the bootloader after installation. This means that bootloader updates must be handled separately, typically by the user or an automated system update process.
For s390x, bootc uses `zipl` instead of `bootupd`.