Problem rebuilding TorizonCore with evaluation containers

I downloaded TorizonCore with evaluation containers 6.1.0-devel-202212+build.4.container for Verdin iMX8M Mini and I installed with Toradex Easy Installer.
It starts, and everything is ok.
Accessing with ssh I copied the file /var/sota/storage/docker-compose/docker-compose.yml (as I read here this is the file that describes which containers should be launched at the boot).
Then I read documentation for torizoncore-builder on how to generate a custom image.
My first attempt is:

  • starting from TorizonCore 6.1.0-devel-202212+build.4 (without evaluation containers)
  • use torizoncore-builder to generate a custom image which is the TorizonCore with evaluation containers, using the proper docker-compose.yml to bundle the desired containers (see here).

I setup a working environment for torizoncore-builder, but when I launch torizoncore-builder bundle ... I see that portainer/portainer-ce and torizon/weston-vivante are pulled properly.
But torizon/chromium cannot be pulled with the following error:

Fetching container image torizon/chromium@sha256:9d363b140a5f4584392432b4ed548c0b6fd5466fbf41b28e834f31924fb62d6d
sha256:9d363b140a5f4584392432b4ed548c0b6fd5466fbf41b28e834f31924fb62d6d: Pulli  sha256:9d363b140a5f4584392432b4ed548c0b6fd5466fbf41b28e834f31924fb62d6d: Pulli  sha256:9d363b140a5f4584392432b4ed548c0b6fd5466fbf41b28e834f31924fb62d6d: Pulling from torizon/chromium 
  Error: no matching manifest for linux/amd64 in the manifest list entries
Stopping DIND container
Error: container images download failed: 404 Client Error for https://127.0.0.1:22376/v1.40/images/torizon/chromium%40sha256:9d363b140a5f4584392432b4ed548c0b6fd5466fbf41b28e834f31924fb62d6d/json: Not Found ("no such image: torizon/chromium@sha256:9d363b140a5f4584392432b4ed548c0b6fd5466fbf41b28e834f31924fb62d6d: No such image: torizon/chromium@sha256:9d363b140a5f4584392432b4ed548c0b6fd5466fbf41b28e834f31924fb62d6d")

And if I look to dockerhub I don’t see any torizon/chromium with the above sha.
Where is my mistake?

Greetings @vix,

The issue is actually shown in the error logs you provided, specifically this line:
Error: no matching manifest for linux/amd64 in the manifest list entries

You must have not specified the platform for the container images. This means for images that provide multiple architectures, like torizon/chromium, Docker will attempt to pull the architecture that matches the system. However, the torizon/chromium image has no “linux/amd64” options so it fails to find any.

If you check the schema for the build command here: TorizonCore Builder Tool “build” command | Toradex Developer Center

You’ll see there’s a property to specify the exact platform for container images to be pulled.

And if I look to dockerhub I don’t see any torizon/chromium with the above sha.

This is actually misleading on Docker Hub. The digest shown on the Web UI isn’t the same digest of the actual image.

Best Regards,
Jeremias

1 Like