Possible bug? Pulling TorizonCore Builder in VS code vs in command prompt

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Hello,

It seems you’re encountering an issue with pulling the TorizonCore Builder tool in VS Code due to an architecture mismatch error (“no matching manifest for linux/arm64/v8”). This discrepancy between VS Code and the command prompt is likely due to differences in Docker configuration.

Here are some steps to help resolve this:

  1. Check Docker Architecture Settings: Ensure that Docker in VS Code is configured to use the correct architecture. This can be done by reviewing the Docker settings in VS Code to match your host system’s architecture.

  2. Verify WSL2 Configuration: Make sure your WSL2 environment is properly set up to work with Docker. Sometimes, VS Code might have different environment variables or settings that affect Docker’s behavior.

  3. Docker Context in VS Code: Confirm that the Docker context in VS Code is set to the correct WSL2 instance. This can be checked in the Docker extension settings within VS Code.

  4. Update VS Code and Extensions: Ensure that both VS Code and the Docker extension are up to date, as updates can resolve compatibility issues.

  5. Compare Environment Variables: Look for any differences in environment variables and Docker settings between your command prompt and VS Code that might be causing the issue.

By following these steps, you should be able to align the Docker behavior in VS Code with that of the command prompt, resolving the architecture mismatch error.

I hope this helps! If you have any more questions, feel free to ask.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Docker error when deploying to device from Torizon Visual Studio plug-in.