Open henrywang opened 1 month ago
When I run bootc install to-existing-root test on aarch64 bare metal server, the bootupd changed boot order to left the bootc system boot first. To re-install a new system, I have to re-configure the boot order to enable network boot first.
bootc install to-existing-root
Installing image: docker://quay.io/redhat_emp1/*****:u2d2 Digest: sha256:1103ab6499bb1bf0f11632bb5afbf7f34e1dd02170127a8c3191de409635188a Initializing ostree layout Initializing sysroot ostree/deploy/default initialized as OSTree stateroot Deploying container image Loading usr/lib/ostree/prepare-root.conf Deployment complete Running bootupctl to install bootloader BootCurrent: 0005 Timeout: 6 seconds BootOrder: 0005,0003,0004,0001,0000,0002,0006,0009 Boot0000 fedora Boot0001* UEFI: Built-in EFI Shell Boot0002 redhat Boot0003* UEFI: PXE IPv4 Intel(R) Network D8:5E:D3:8F:A5:04 Boot0004* UEFI: PXE IPv4 Intel(R) Network D8:5E:D3:8F:A5:05 Boot0006 Fedora Boot0009 Gemini Boot0005* redhat Installed: grub.cfg Installed: "redhat/grub.cfg" Installation complete!
The RFE here I think is for an option to preserve the existing boot order. Some use cases are likely relying on us replacing it.
When I run
bootc install to-existing-root
test on aarch64 bare metal server, the bootupd changed boot order to left the bootc system boot first. To re-install a new system, I have to re-configure the boot order to enable network boot first.