docs: Add initramfs day two options and future - #2415
Conversation
Signed-off-by: Joseph Marrero Corchado <jmarrero@redhat.com>
| Some systems need machine-specific initramfs content after installation, such | ||
| as a udev rule required to unlock local storage. Until `bootc` has a dedicated |
There was a problem hiding this comment.
Well the details of what one wants to do in the initramfs matter a lot here.
Like, does the udev rule itself actually need to be machine specific?
A general pattern that also works is to have "machine specific" configuration embedded in generic images that dispatches on machine specific identifiers hardware MAC addresses are a classic option, but not the only one.
|
|
||
| COPY 98-thunderbolt.rules /etc/udev/rules.d/98-thunderbolt.rules | ||
|
|
||
| RUN set -eu; \ |
There was a problem hiding this comment.
This is operating system specific, I think we should just link to https://docs.fedoraproject.org/en-US/bootc/initramfs/
| Build the image locally, then stage it through the Podman container storage: | ||
|
|
||
| ```console | ||
| $ sudo podman build --security-opt=label=disable --pull=newer \ | ||
| --tag localhost/machine-bootc:latest . | ||
| $ sudo bootc switch --transport containers-storage localhost/machine-bootc:latest | ||
| $ sudo systemctl reboot | ||
| ``` |
There was a problem hiding this comment.
Do we need to duplicate these instructions vs just referencing the booting-local-builds.md?
| whenever either the base image or the machine-specific initramfs configuration | ||
| changes. A systemd service and timer can automate the rebuild if required. | ||
|
|
||
| ### Automate the local build |
There was a problem hiding this comment.
This is a fully generic instruction that I think makes more sense in the booting-local-builds.md
BTW, the real problem with this is correct change detection; if you don't have reproducible builds then you're going to be pointlessly rebooting your machine some days...
2 participants
No description provided.