I started getting a * no matching manifest for linux/arm64/v8 in the manifest list entries
error when building a c++ project .
After spinning my tires a bit I decided to just uninstall, VC Code, WSL2, and Docker. Figuring it was something that got messed up. I reinstalled everything and I still get the error.
I clicked on New torizon project
selected c++ application
Compiled the local amd 64 just to make sure it worked (and it did)
Connected my Toradex SOM via the extension, and set it to default.
Ran the Torizion ARMv8 tasks
Looks like it built the container and pushed it, but when it goes to pull it, it gives me the error.
So, odd the extension usually just works. I had no issues up until today. I really need to fix this to keep working on a clients project
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, it seems that the error you’re encountering is due to the Docker image not having a compatible version for the ARM64 architecture. Here are some steps you can take to resolve this issue:
Check Docker Image Compatibility: Verify that the Docker image you are trying to use has an ARM64 version available. You can do this by checking the image’s page on Docker Hub or its documentation to see if it supports multi-architecture builds.
Build Your Own Image: If the image does not support ARM64, you might need to build your own Docker image. You can create a Dockerfile that targets the ARM64 architecture and build the image yourself. This ensures that the image is compatible with your Toradex SOM.
Consult Torizon Documentation: Review the Torizon documentation for any specific instructions or requirements regarding ARM architecture support and Docker image usage. There might be additional steps or configurations needed for ARM64.
Community Support: If the issue persists, consider reaching out to the Torizon community or Toradex support. They might have encountered similar issues and could provide additional insights or solutions.
These steps should help you address the error and continue working on your project. If you have already tried these steps and the issue persists, it might be helpful to provide more specific details or logs to the community or support for further assistance.
Please, also check if these links can help you solve your problem:
I reinstalled everything again and this time used the wizard from the extension. After that it’s a similar error. The thing I I can see the image is on my host machine.
I see you’re doing this on Windows/WSL2. In my experience Docker/containers can be a bit more “temperamental” on Windows compared to Linux. That said let me just list some things that I know have been an issue in the past for others and you can check on your side.
First of all just to confirm, is 192.168.0.121 the IP address of your Toradex device, and is 192.168.0.120 the IP address of your development PC?
On your Toradex device, if you attempt to manually pull the debug container via the console do you get the same error as shown in the extension?
When you re-installed everything did you install Docker Desktop on Windows? Or did you install the Docker engine in WSL2? You should only have one of these installed, preferably Docker engine in WSL2. I’ve seen other users have both of these installed and it resulted in weird interactions between both Docker installations, they don’t seem to play nice together.
If you only have Docker Desktop on Windows installed, did it update recently? I’ve seen some cases where Docker Desktop had an update that would kinda break things with our extension. This might be what happened on your side since you said it worked until recently.
I solved the issue. In the setting of Docker desktop under General there is a check box “Use containerd for pulling and storing images” When this box is checked you will get the “a * no matching manifest for linux/arm64/v8 in the manifest list entries” error. I unchecked it and everything worked again. I think this got checked when I upgraded docker desktop
Huh interesting. I have Docker Desktop installed on my Windows laptop for a while now. If I check my settings this option is unchecked, and I don’t recall ever unchecking it myself. Maybe having this option checked is the new default on Docker Desktop?
In any case glad you were able to resolve this, and thank you for sharing your findings.
I had the same problem while trying to build a container for my Python project under Linux (Ubuntu 22.04). The solution suggested by @jeffbelz also works for Linux development computers should anyone encounter this problem too.
