Skip to content

Commit

Permalink
docs: Move kernel/initramfs from install to base image doc
Browse files Browse the repository at this point in the history
We have this in other places, but it's best here. At some
point I might redirect the other copies here.

Signed-off-by: Colin Walters <[email protected]>
  • Loading branch information
cgwalters committed Nov 8, 2024
1 parent 680b29f commit 700faa6
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions docs/src/bootc-images.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,16 @@ You can then use `podman build`, `buildah`, `docker build`, or any other contain
build tool to produce your customized image. The only requirement is that the
container build tool supports producing OCI container images.

## Kernel

The Linux kernel (and optionally initramfs) is embedded in the container image; the canonical location
is `/usr/lib/modules/$kver/vmlinuz`, and the initramfs should be in `initramfs.img`
in that directory. You should *not* include any content in `/boot` in your container image.
Bootc will take care of copying the kernel/initramfs as needed from the container image to
`/boot`.

Future work for supporting UKIs will follow the recommendations of the uapi-group in [Locations for Distribution-built UKIs Installed by Package Managers](https://uapi-group.org/specifications/specs/unified_kernel_image/#locations-for-distribution-built-ukis-installed-by-package-managers).

## The `ostree container commit` command

You may find some references to this; it is no longer very useful
Expand Down

0 comments on commit 700faa6

Please sign in to comment.