Skip to content

Adding custom BLS entry blocks most bootc operations #2228

Description

@Dudecake

bootc status gives an "efi does not start with custom prefix" error if a custom BLS entry is present.

‎BLSConfig::get_verity expects entries for .efi files to be UKI's with a name starting with bootc_composefs-

[archlinux ~]# bootc status                         
error: Status: Getting composefs deployment status: Getting composefs deployment status: Listing bootloader entries: efi does not start with custom prefix
[archlinux ~]# mv /boot/loader/entries/fwupd.conf{,.bak}
[archlinux ~]# bootc status                             
● Booted image: 192.168.122.1/bootc-iot
        Digest: sha256:b71bd3f9e704a0c41e5722227c0181700062e4a46d0e9839de5df43c9dd52d86 (amd64)
        Verity: 1b58308f766da92eb21c7fb8c3a016d4bb5315a4b70771e014d906c2a8036f2040d625cc145986b3a8c2328cefee16c342d0d0de24b835fff1768f4476a2fe0a
       Version: latest (2026-06-03T07:44:07Z)

  Rollback image: 192.168.122.1/bootc-iot
          Digest: sha256:d6b21a4d2b0eb2cd0694ee71f2dcfc5720f2698b2c0324bcd364829688bfc668 (amd64)
          Verity: 29d1f17c5d2b8c6e86d28eb4d5df4a1ec9f7d2a7e34cd6f238bae668e9cd86310c14b17f1d4e73e353d54b57ee5702b2a291ebd1e4a62dccaa7d61bd8ece00ec
         Version: latest (2026-05-27T21:35:58Z)

Contents of /boot/loader/entries:

==> /boot/loader/entries/bootc_arch-1b58308f766da92eb21c7fb8c3a016d4bb5315a4b70771e014d906c2a8036f2040d625cc145986b3a8c2328cefee16c342d0d0de24b835fff1768f4476a2fe0a-1.conf <==
title Arch Linux
version 1b58308f766da92eb21c7fb8c3a016d4bb5315a4b70771e014d906c2a8036f2040d625cc145986b3a8c2328cefee16c342d0d0de24b835fff1768f4476a2fe0a
linux /EFI/Linux/bootc_composefs-1b58308f766da92eb21c7fb8c3a016d4bb5315a4b70771e014d906c2a8036f2040d625cc145986b3a8c2328cefee16c342d0d0de24b835fff1768f4476a2fe0a/vmlinuz
initrd /EFI/Linux/bootc_composefs-1b58308f766da92eb21c7fb8c3a016d4bb5315a4b70771e014d906c2a8036f2040d625cc145986b3a8c2328cefee16c342d0d0de24b835fff1768f4476a2fe0a/initrd
options rw composefs=1b58308f766da92eb21c7fb8c3a016d4bb5315a4b70771e014d906c2a8036f2040d625cc145986b3a8c2328cefee16c342d0d0de24b835fff1768f4476a2fe0a
sort-key bootc-arch-0

==> /boot/loader/entries/bootc_arch-29d1f17c5d2b8c6e86d28eb4d5df4a1ec9f7d2a7e34cd6f238bae668e9cd86310c14b17f1d4e73e353d54b57ee5702b2a291ebd1e4a62dccaa7d61bd8ece00ec-0.conf <==
title Arch Linux
version 29d1f17c5d2b8c6e86d28eb4d5df4a1ec9f7d2a7e34cd6f238bae668e9cd86310c14b17f1d4e73e353d54b57ee5702b2a291ebd1e4a62dccaa7d61bd8ece00ec
linux /EFI/Linux/bootc_composefs-d9df04000c701c246c77f8937b960bbcff55e3122748915d6c794548e5611bd0dd4492d1da3451a420cd7ea3d47c4236885606a58f6fa99c9e0bb422ff3a523f/vmlinuz
initrd /EFI/Linux/bootc_composefs-d9df04000c701c246c77f8937b960bbcff55e3122748915d6c794548e5611bd0dd4492d1da3451a420cd7ea3d47c4236885606a58f6fa99c9e0bb422ff3a523f/initrd
options rw composefs=29d1f17c5d2b8c6e86d28eb4d5df4a1ec9f7d2a7e34cd6f238bae668e9cd86310c14b17f1d4e73e353d54b57ee5702b2a291ebd1e4a62dccaa7d61bd8ece00ec
sort-key bootc-arch-1

==> /boot/loader/entries/fwupd.conf <==
title      Firmware updater
version    2.1.1
efi        /EFI/boot/fwupdx64.efi

Entries not starting with bootc_ should probably be skipped as installing things like fwupd or memtest86+ shouldn't block updates

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions