Source tcb-env-setup.sh thinks it's source tcbbuilder to a arm64 host

Technical Support
, , ,
4

Based on your follow-up, it seems the issue persists despite the version changes. The key problem appears to be that ARM emulation is not properly configured on your system. Here are the specific steps to resolve this:

Enable ARM Emulation

ARM emulation is not persistent and must be enabled at every boot (1). Run this command to enable ARM emulation:

$ docker run --rm -it --privileged torizon/binfmt

(1)

Verify ARM Emulation is Working

After enabling ARM emulation, test it with these commands:

Test arm64v8:

$ docker run --rm -it --pull always --platform linux/arm64/v8 debian arch

(1)

The return should be:

aarch64

(1)

If this test fails, the ARM emulation is not working properly, which explains why you’re getting the “no matching manifest” error.

Docker Configuration Check

Since you mentioned forcing --platform=amd64 works but then fails when the system tries to use it, verify your Docker installation:

  1. Ensure single Docker installation: Make sure you only have Docker Engine in WSL2, not both Docker Engine and Docker Desktop (2)
  2. Check Docker version: Confirm you’re actually running Docker 28.5.2:
    docker --version

TorizonCore Builder Specific Issue

The tcb-env-setup.sh script is trying to pull ARM64 containers on your x86 system. This requires ARM emulation to be properly configured. The script expects to be able to run ARM containers through emulation.

Alternative Approach

If ARM emulation continues to fail, you may need to run TorizonCore Builder on a native ARM64 system or use a different approach. However, the standard workflow is to run it on x86 with ARM emulation enabled (1).

Try the ARM emulation setup first - this is the most common cause of the issue you’re experiencing.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.