SecureBoot - Preloaded Image not flashing containers

I’ve been attempting to get SecureBoot working within our offline provisioning process and having some issues. Doing the exact same process without secureboot yields a successful installation using the “balena preload” command with all of our relevant configuration.

Using balena CLI v17+ with the “–secureBoot” flag generates a flashable image – it just doesn’t deposit the containers (or at least doesn’t start them).

Hi, I understand you are preloading a secure boot image that does not correctly install the preloaded containers. Is that right?

Could you please provide us with the complete balenaCLI preloading command you are using, as well as the version of balenaOS? With those details we will try to reproduce.

Hey @alexgg yes that is correct. It installs the OS with secureboot but does not include the preloaded containers.

#!/bin/bash

balena os download generic-amd64 -o $(pwd)/bc_amd64_4.0.25.img --version 4.0.25

balena preload $(pwd)/bc_amd64_4.0.25.img --fleet <redacted> -p -s $(pwd)/SUPPORTS/balena-logo.png --commit <redacted>

balena os configure $(pwd)/bc_amd64_4.0.25.img --secureBoot --config $(pwd)/SUPPORTS/config.json --fleet <redacted> -c $(pwd)/SUPPORTS/system-connections/hd-signage -c $(pwd)/SUPPORTS/system-connections/kore_vzw -c $(pwd)/SUPPORTS/system-connections/kore_ATT -c $(pwd)/SUPPORTS/system-connections/kore_Tmobile --version 4.0.25

@alexgg I’ve been testing to confirm – and doing the same script without secureboot is working as-expected.