Containers to be used to test Torizon OS 7

[vix]

I see that in the integration feeds the first monthly release of Torizon OS 7 for Verdin iMX8M-Plus is available (7.0.0-devel-202409+build.1).
I’m going to start my testing on this release, so that I cab give feedback and be ready for a smooth transition when the first LTS is released.
My question is: which tag should I pull for the several torizon/... containers on Dockerhub with Torizon OS 7? Is this next tag?
Basically I’m interested in:

• weston-vivante
• chromium
• cog

Which debian-slim release they’re based on? So that I can build my custom containers maximising the layer caching.

Thanks

[ToradexAI]

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

Did you like my answer?

---

For testing Torizon OS 7, you should use the next tag for the torizon/... containers on Docker Hub. This tag is typically used for the latest development versions, which would align with your testing of the Torizon OS 7 release.

Regarding the Debian release they are based on, the containers are derived from a minimal variant of the Debian Bookworm release. This should help you in building your custom containers while maximizing layer caching.

Here are the specific tags you should pull for the containers you mentioned:

• torizon/weston-vivante:next
• torizon/chromium:next
• torizon/cog:next

By using these tags, you will ensure that you are working with the most recent development versions that are compatible with Torizon OS 7.

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

High performance, low power Embedded Computing Systems | Toradex Developer...

Imx8: weston: add 'use-g2d' option as default

Hi @leon.tx I’ve just seen your commit here on next branch of weston container for imx8 platform. In the commit comment I read: This is a new switch from Weston 10 (which previously seems to have been enabled all the time). This flag tells Weston to load the g2d renderer libraries that come from libg2d-viv. Related-to: TCCP-768 I’m curious; if I’m right, Torizon OS 6.7 (and 6.8 too) comes with weston 10.0.1 Did you add that command line switch because you saw some graphic performance…

Running a Weston container on torizon mit Weston-vivante container.

[jeremias.tx]

Greetings @vix,

My question is: which tag should I pull for the several torizon/... containers on Dockerhub with Torizon OS 7? Is this next tag?

Correct everything for Scarthgap can be found in the next tag for the container images.

Which debian-slim release they’re based on? So that I can build my custom containers maximising the layer caching.

Currently at the time of writing, the containers are using 12.6-slim as a base. You can see in our CI build file here: torizon-containers/.gitlab-ci.yml at next · torizon/torizon-containers · GitHub

I’m sure you already know, but keep in mind everything Scarthgap is a work-in-progress and the our team is still heavily iterating on many components.

Best Regards,
Jeremias

[vix]

@jeremias.tx

Correct everything for Scarthgap can be found in the next tag for the container images.

to summarize, form Verdin iMX8M-Plus:

• torizon/weston-imx8:next (no more weston-vivante but weston-imx8 for Scarthgap)
• torizon/chromium-imx8:next (specific build for imx8 architecture)
• torizon/cog:next (generic build for arm64 architecture)

Can you confirm the above list?

I’m sure you already know, but keep in mind everything Scarthgap is a work-in-progress and the our team is still heavily iterating on many components.

I know, but I would like giving my feedback to the team from a customer usage scenario.

[leon.tx]

Can you confirm the above list?

There’s cog-imx8:next as well.

We’re migrating the tests to the repo itself now, so you can use the docker run... statements there found there torizon-containers/tests/suites/imx8 at next · torizon/torizon-containers · GitHub.