I ran updates on my build computer recently, and I can’t seem to get bitbake to build the image. The following output is from a completely stock build following the instructions exactly:
workstation:/code/torizon/aquila-am69$ mkdir oe-core-7.x.y.20251106.stock
workstation:/code/torizon/aquila-am69$ cd oe-core-7.x.y.20251106.stock/
workstation:/code/torizon/aquila-am69/oe-core-7.x.y.20251106.stock$ ls
workstation:/code/torizon/aquila-am69/oe-core-7.x.y.20251106.stock$ repo init -u git://git.toradex.com/toradex-manifest.git -b scarthgap-7.x.y -m torizon/default.xml
Downloading Repo source from /code/torizon/aquila-am69/oe-core-7.x.y.20251106/.repo/repo/.git
remote: Enumerating objects: 9423, done.
remote: Counting objects: 100% (9423/9423), done.
remote: Compressing objects: 100% (4323/4323), done.
remote: Total 9423 (delta 5017), reused 9423 (delta 5017), pack-reused 0
Your identity is: <@users.noreply.github.com>
If you want to change this, please re-run ‘repo init’ with --config-name
repo has been initialized in /code/torizon/aquila-am69/oe-core-7.x.y.20251106.stock
workstation:/code/torizon/aquila-am69/oe-core-7.x.y.20251106.stock$ repo sync --no-clone-bundle
Syncing: 94% (18/19), done in 41.625s
Syncing: 100% (19/19) 0:43 | 1 job | 0:01 bitbake.git @ layers/openembedded-core/bitbakerepo sync has finished successfully.
workstation:/code/torizon/aquila-am69/oe-core-7.x.y.20251106.stock$ MACHINE=aquila-am69 source setup-environment
Welcome to Toradex Torizon OS
For more information about OpenEmbedded see their website:
Your build environment has been configured with:
MACHINE = aquila-am69
SDKMACHINE = x86_64
DISTRO = torizon
You can now run ‘bitbake ’
Some of common targets are:
torizon-docker
torizon-minimal
torizon-podman
workstation:/code/torizon/aquila-am69/oe-core-7.x.y.20251106.stock/build-torizon$ bitbake torizon-docker
ERROR: User namespaces are not usable by BitBake, possibly due to AppArmor.
See Ubuntu 24.04 LTS (Noble Numbat) Release Notes - Release - Ubuntu Community Hub for more information.
Summary: There was 1 ERROR message, returning a non-zero exit code.