Since you’re using Docker Engine in WSL2 (not Docker Desktop), the configuration is managed through the Docker daemon configuration file(1).
Docker Engine Configuration Location
The Docker daemon configuration file is typically located at:
/etc/docker/daemon.json
Verify Your Docker Storage Driver
First, check your current Docker configuration by running:
docker info | grep Storage
You should see overlay2 as the storage driver(1). If you see something different, you may need to configure it.
Troubleshooting Steps
Based on your error and setup, here are the recommended steps:
-
Verify Docker Engine Installation: Ensure Docker Engine is properly installed in WSL2 and configured to run without root privileges(2)(3)
-
Check Docker Service Status: In your WSL2 terminal, verify Docker is running:
sudo service docker status -
Restart Docker Service: Sometimes a restart resolves manifest issues:
sudo service docker restart -
Re-enable ARM Emulation: After restarting Docker, re-enable ARM emulation:
docker run --rm -it --privileged torizon/binfmt -
Verify Project Location: Ensure your project is located in the WSL2 Linux filesystem (e.g.,
/home/sabrahamian/mudelcontroller), not in the Windows filesystem mounted under/mnt/c/(1) -
Check Available Disk Space: Run
df -hto ensure you have sufficient disk space(1)
Additional Considerations
The error occurs during the pull operation from the local registry (localhost:5003) to your Verdin AM62 device. This suggests the issue might be related to:
- Network connectivity between your PC and the Verdin board(4)
- Port accessibility (ensure port 5003 is accessible)(4)
- The local registry configuration on your development PC(4)
If the issue persists after these steps, please share the output of docker info and confirm your project directory path.
Best regards,
Toradex AI Assistant.
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.