Blazer project for arm gives Manifest unknown

Technical Support
,
4

Issue Analysis

Looking at your output, I can see that ARM emulation is working correctly - the armv7l response confirms this (1). The issue appears to be in the Docker build process or registry configuration.

Key Observations

From your build log, I notice several important points:

1. Build Arguments Are Correct

Your build shows:

--build-arg IMAGE_ARCH=arm

This is the correct setting for iMX7 (1).

2. Registry Push Appears Successful

The build log shows:

[+] push 16/17
⠙ localhost:5002/blazer1:v0.0.0 [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] Pushing

3. Port Tunnel is Working

The registry tunnel setup appears successful:

Registry ready

Potential Solutions

1. Docker Desktop Configuration Issue

Based on similar issues reported in the community, this could be related to Docker Desktop’s “containerd” setting (2). If you’re using Docker Desktop, check if the “Use containerd for pulling and storing images” option is enabled and try disabling it (2).

2. Registry Synchronization Issue

There might be a timing issue between the push and pull operations. Try these steps:

  1. Verify the image was pushed correctly by checking the registry from your development machine:
curl http://localhost:5002/v2/blazer1/manifests/v0.0.0
  1. Check if the registry tunnel is working from the target device:
curl http://localhost:5002/v2/_catalog

3. Manual Registry Verification

On your target device (192.168.10.103), verify the registry is accessible:

curl http://localhost:5002/v2/blazer1/tags/list

4. Clean Build Process

Try a complete clean build:

  1. Stop all containers and clean the local registry:
docker system prune -a
  1. Rebuild the project from scratch using the Torizon IDE extension.

Architecture Verification

To verify your Dockerfile is correctly configured, ensure it uses the IMAGE_ARCH build argument properly. For .NET Blazor projects, the Dockerfile should contain something like:

FROM --platform=linux/${IMAGE_ARCH} torizon/aspdotnet8:4

The fact that your build log shows linux-arm/publish in the COPY command suggests the architecture is being set correctly during the build process.

Next Steps

  1. Check Docker Desktop settings if applicable (2)
  2. Verify registry connectivity from both sides
  3. Try a manual pull after ensuring the registry tunnel is stable
  4. Check for any firewall issues that might affect the registry tunnel

The issue seems to be in the registry communication rather than the ARM emulation or build process itself.

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.