I believe I know what’s happening here. Currently we have containers based on Debian bullseye. We plan to release new containers based on Debian bookworm. This is because between TorizonCore 6.X.Y and 5.X.Y the kernel version differs quite a bit along with other things. So I imagine the packages and drivers in the current Debian bullseye containers aren’t entirely compatible with the new system in TorizonCore 6.X.Y.
That said the new Debian bookworm based containers aren’t quite ready yet. The team is currently working on finishing the new containers. Once these are out I suspect the 3D rendering capabilities should work again.
If possible I would ask you to please wait for the new containers as these are the containers that are meant for TorizonCore 6.X.Y.
All the bookworm containers are still not ready yet as you noticed. In fact we only just bumped the version of the Weston container in the evaluation image to bookworm about 2 days ago. You can see this if you’re using a very recently built nightly image (within the last few days):
torizon@verdin-imx8mm-06827778:~$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
torizon/weston-vivante 3 779d54f7f4d1 2 weeks ago 510MB
portainer/portainer-ce 2.17.1 ada025d39772 2 weeks ago 267MB
torizon/chromium 2 cb7ac4913734 6 months ago 609MB
torizon@verdin-imx8mm-06827778:~$ cat /etc/issue
TorizonCore with PREEMPT_RT 6.2.0-devel-20230315+build.210 \n \l
However we have still not bumped the chromium container to bookworm yet. In fact there is no chromium bookworm container yet as the team still needs to create this.
thanks to your email I discovered two interesting things:
not all the bookworm-based containers have been already released. I hope for the booworm chromium soon
The page to download binaries has some problmes with the links: today you can see it sould point to build 210, but if you link on the Verdin iMX8M Mini, the link points to build 202.
This explains why I think I downloaded build 209 (yesterday), but I got the files for build 202 (which has weston-vivante:2).
Some of the links point to the right build 210, some to 209, some others to 202.
On the other side, it seems that the links for TorizonCore (without Evaluation Containers) point to build 210 for all the devices.
Not all of our nightly builds succeed. So when we do build 210 for example maybe some devices fail to build or have other issues, in these cases those builds are not published. When that happens the links just point to the latest successful build for those modules.
And can you share a roadmap for the release of chromium:3 container (bookworm-based)?
I do not have any definite roadmap or timeline I can share at the moment. All I can say is that the bookworm chromium container is in progress and is one of the last containers that need to be updated to bookworm.
Hi @jeremias.tx ,
after a deeper investigation I have some other doubts on what happens to the download links.
As I wrote, yesterday the link for iMX8M-Mini pointed to build 202, and you gave a possible explanation.
Moreover, the link on the left part of the page 6.2.0-devel-20230315+build.210.container opens a page with toradex artifacts, and it seems that the build 210 is there, so it didn’t fail.
Do you mean it has other issues?
That is odd, perhaps there’s something wrong with the automation that is publishing these links to our developer site. Let me check with the responsible team and see if they know what’s going on with this.