Repository navigation
Fix Marlin boot backend and filesystem defaults - #413
Merged
Merged
Conversation
hanthor
force-pushed
the
fix/marlin-installer-defaults
branch
from
October 4, 2026 05:06
8cea208 to
01fae27
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Marlin ships bootupctl alongside systemd-boot but no GRUB update payload. Corral selected OSTree/XFS and the real AWS KubeVirt install failed with
bootupd is required for ostree-based installs.Inspect both legacy and current GRUB payload layouts before selecting OSTree. Otherwise systemd-boot selects composefs, with ext4 when its formatter exists and btrfs for existing btrfs-only images. Give the filesystem-only podman probe an explicit inert command for OS images without CMD/ENTRYPOINT. Update both cluster and local selection paths.
Validation: bootc-tagged Go tests for pkg/bootc, pkg/kubevirt and cmd pass, including both GRUB payload layouts taking precedence over an installed systemd-boot binary. Both the local Go probe and the actual rendered cluster selection script report composefs/ext4 against ghcr.io/tuna-os/marlin:gnome. A real AWS KubeVirt installation is in progress; boot is not yet qualified.