Cannot pull from WSL

Technical Support
,
1

Hello everyone!

I set up a new Windows PC.
Installed Docker Desktop and VS Code from scratch.
Installed WSL2 with Ubuntu 24.04.
Installed Torizon IDE…

Whenever I set up a new project (just the HelloWorld versions), whether in C#, C++, or Python:

I always get the following error after the respective debug containers have been built:

Executing task: DOCKER_HOST=10.100.1.79:2375 LOCAL_REGISTRY=10.100.1.2 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose pull pytest-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.[+] Pulling 0/1⠙ pytest-debug Pulling                                                                                                                                                                                                                   0.1sWARNING: Some service image(s) must be built from source by running:docker compose build pytest-debugno matching manifest for linux/arm64/v8 in the manifest list entries


  The terminal process “/usr/bin/bash ‘-c’, ‘DOCKER_HOST=10.100.1.79:2375 LOCAL_REGISTRY=10.100.1.2 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose pull pytest-debug’” failed to launch (exit code: 1).

run-share-wsl-ports results e.g. in:

 *  Executing task: xonsh /home/gerko/Toradex/DotnetTest/.conf/share-wsl-ports.xsh /home/gerko/Toradex/DotnetTest 


 *  The terminal process failed to launch: Cannot launch a terminal process in an untrusted workspace with cwd \home\gerko\Toradex\DotnetTest and userHome \home\gerko.

I suspect some ‘simple’ setting is missing on my end.
docker build is working perfectly in all projects.

Can someone help me?
Best
Gerald

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Solution for “no matching manifest for linux/arm64/v8” Error

The error you’re encountering is a known issue with Docker Desktop configuration. This has been reported by other users and has a straightforward solution.

Primary Solution: Docker Desktop Settings

The issue is caused by a Docker Desktop setting that interferes with multi-architecture image pulling (1). To resolve this:

  1. Open Docker Desktop settings
  2. Navigate to the General tab
  3. Uncheck the “Use containerd for pulling and storing images” option (1)
  4. Restart Docker Desktop

This setting can get automatically enabled during Docker Desktop updates, which explains why it worked before and suddenly stopped (1).

Docker Installation Recommendation

For Torizon development, we recommend using Docker Engine in WSL2 rather than Docker Desktop on Windows (2). This approach is more reliable and avoids licensing considerations:

  1. Open a WSL terminal by running wsl in PowerShell (2)
  2. Install Docker Engine in WSL following the instructions for your specific Linux distribution (2)
  3. Configure Docker to run without root privileges (2)

Environment Issues

Regarding your second error about the untrusted workspace, this appears to be a VS Code workspace trust issue. Ensure you’ve marked your workspace folder as trusted in VS Code.

Verification Steps

After applying the Docker Desktop fix:

  1. Try pulling a debug container again
  2. Verify that docker build continues working
  3. Test deployment to your target device

The “no matching manifest for linux/arm64/v8” error specifically occurs when Docker incorrectly detects or requests ARM64 architecture images that don’t exist for certain containers (1).

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.

3

This is the solution.

1 Like