Hi @jeremias.tx
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.
But today, the same link points to build 26 of last August.
I cannot see the reason, actually.
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.
You can see from this news that Bookworm is (kind of) already available, but the documentation was not yet updated: TorizonCore 6.2.0 Quarterly Release
You can see in Docker Hub, e.g. for the Debian container: Docker
If you really want, you can try it, but I think it makes sense to wait for the documentation to be updated because it is possible that the documentation for Bullseye is not totally compatible with Bookworm.
I see that the news has been published today.
Great news!
In a few days I expect to download TorizonCore with Evaluation Containers binaries where the containers are bookworm-based.
The last Nightly has bullseye-based containers (weston-vivante, chromium, portainer-ce).
Just to clarify, the bookworm versions of the Chromium and Cog containers are still not available as stated in the 6.2.0 release news.
Thank you.
I’ve been confused by this commit that bumped conmtainer tags to bookworm (CT_TAG_CHROMIUM and CT_TAG_COG too).
But I canot easy understand which meta-toradex-torizon commit is used in the several TorizonCore builds (Quarterly, Monthly, Nightly).
not yet;
based on what I see in the past (i.e., issues mixing bullseye and bookworm containers), I prefer wating for Chromium:3 bookworm before trying again.
Hi @henrique.tx
yes I tried.
Basically the Chromium Bookworm Container works for a simple web page.
But the behavior with 3D content is not ok.
It seems that Vulkan is not enabled (or something like that), but I need some more time to investigate.
I let you know.
).