Skip to content

Commit 726041f

Browse files
authored
Merge pull request #1354 from cgwalters/doc-bootloader
docs: Add bootloaders.md
2 parents 9d15eed + 88a830a commit 726041f

File tree

2 files changed

+10
-0
lines changed

2 files changed

+10
-0
lines changed

docs/src/SUMMARY.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,7 @@
5151
- [Filesystem](filesystem.md)
5252
- [Filesystem: sysroot](filesystem-sysroot.md)
5353
- [Container storage](filesystem-storage.md)
54+
- [Bootloader](bootloader.md)
5455

5556
# Experimental features
5657

docs/src/bootloaders.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Bootloaders in `bootc`
2+
3+
`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).
4+
5+
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.
6+
7+
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.
8+
9+
For s390x, bootc uses `zipl` instead of `bootupd`.

0 commit comments

Comments
 (0)