Secure boot with bundled docker images into Torizon

Technical Support
2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello KV,

Thank you for reaching out with your question. It sounds like you’re encountering an issue with dm-verity failing to verify your Torizon image after bundling Docker images. This is likely related to the integrity verification process, which is crucial when secure boot is enabled.

Here are some steps you can take to resolve this:

  1. Ensure Proper Signing: After adding Docker images to your Torizon image, make sure the entire image is re-signed. The addition of Docker images can change the image’s hash, which must be updated in the signature for dm-verity to verify it correctly.

  2. Use TorizonCoreBuilder Correctly: Ensure you are following the recommended workflow for TorizonCoreBuilder. Use the bundle command to download and prepare Docker images, and then the combine command to integrate these images into your Torizon image.

  3. Verify Image Integrity: Before deploying, verify the image’s integrity using appropriate tools to ensure all components, including Docker images, are correctly signed and verified.

  4. Check Configuration: Review your local.conf and other configuration files to ensure all settings related to secure boot and dm-verity are correctly configured.

By following these steps, you should be able to maintain the integrity of your Torizon image with bundled Docker images, allowing dm-verity to verify it successfully.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Torizon Core Builder.