Hi, I’m the Toradex AI Assistant.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Did you like my answer?

Hello! Thank you for sharing the details of your environment and the error you are seeing when building a Yocto/OpenEmbedded image for your Colibri iMX7 eMMC 1GB module.
The error you are experiencing is related to the post-installation script for the shadow package. Specifically, it is failing during the root filesystem creation (do_rootfs
), and Yocto is no longer supporting deferred postinstall scripts—so it cannot be postponed to the first boot.
Here are some practical steps to resolve this issue:
1. Check Your local.conf
Configurations
Ensure your local.conf
contains the following for the Colibri iMX7:
MACHINE ?= "colibri-imx7-emmc"
ACCEPT_FSL_EULA = "1"
- Ensure the
MACHINE
variable matches your module (colibri-imx7-emmc
for eMMC modules).
ACCEPT_FSL_EULA = "1"
is required for NXP-based SoMs.
More details: Building a Reference Image with Yocto Project/OpenEmbedded
2. Clean and Rebuild
Sometimes old build artifacts can cause persistent issues. Try cleaning and rebuilding the problematic image with:
bitbake -c clean tdx-reference-minimal-image
bitbake tdx-reference-minimal-image
3. Read the Detailed Log
Check the log file mentioned in your error output (log.do_rootfs
). Look for lines around the shadow postinstall step. Often problems relate to:
- Missing build dependencies
- File system incompatibilities
- Misconfigured package users/groups
4. Update Host Packages
Ensure your host system is up-to-date, and that all required host build dependencies (like python3
, tar
, xz
, gcc
, etc.) are installed.
5. Remove Unnecessary exit 1
Workarounds
As of recent Yocto versions, adding exit 1
in postinstall scripts to defer to first boot is NOT supported. Do not manually modify any postinst scripts to do this.
6. Use Supported BSP/Yocto Version
You are using BSP 6.8.0 (hardknott-based). Ensure all your meta-layers are checked out at compatible branches/commits for this BSP. Mismatched branches can cause postinstall and packaging issues.
More Information
Visit these links for more guidance:
If the log indicates a problem with user or group creation (typical for shadow issues), make sure no conflicting files exist in your custom layers.
Let me know if examining the log or these changes help resolve your issue, or if you need guidance on a specific error line from the detailed log.
Best regards,
Toradex AI Assistant.