Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
This error is typically related to Docker version compatibility issues and ARM emulation configuration. Here are the most likely causes and solutions:
Docker 29 Incompatibility
If you’re using Docker v29, this is a known compatibility issue(1). The error occurs when Docker v29 attempts to pull container images with platform manifests(1).
Solution: Update to Torizon IDE Extension Version 3.3.114 (pre-release) which fixes this issue(1). Alternatively, you can downgrade your Docker installation to version 28.x as a workaround(1).
Docker Desktop Configuration Issue
If you’re using Docker Desktop, check the “Use containerd for pulling and storing images” setting(2). When this option is enabled, it can cause the “no matching manifest for linux/arm64/v8” error(2).
Solution: In Docker Desktop settings under General, uncheck “Use containerd for pulling and storing images”(2).
ARM Emulation Not Enabled
ARM emulation is not persistent and must be enabled at every boot(3). This commonly causes exec format error when building or running ARM containers on x86 platforms(3).
Solution: Enable ARM emulation by running:
$ docker run --rm -it --privileged torizon/binfmt
Docker Installation Conflicts
Ensure you have only one Docker installation - either Docker Engine in WSL2 OR Docker Desktop on Windows, not both(2). Having both installed can result in weird interactions(2).
Recommendation: Use Docker Engine in WSL2 rather than Docker Desktop, as Docker Desktop is licensed under the Docker Subscription Service Agreement while Docker Engine uses the Apache License, Version 2.0(4).
Try these solutions in order, starting with checking your Docker version and the containerd setting if using Docker Desktop.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.