Currently, we are in the process of developing and producing our own Boot2Qt based image, which you can learn more about here: How to Create Boot to Qt Image | Boot to Qt 6.5.2.
In addition to this, we have implemented our custom meta-layer that introduces various drivers and features. Our application utilizes serial ports and CAN Bus functionality. Given that this application serves as the primary GUI for our device, it also facilitates the adjustment of local settings such as static IP configuration, device shutdown and reboot, timezone settings, and more.
Looking ahead, we anticipate incorporating Docker support to enable the deployment of multiple features like mariadb. Furthermore, we’re interested in integrating an over-the-air (OTA) update capability, potentially using SWUpdate or OSTree.
At this juncture, Torizon appears to align well with our requirements. However, after thorough experimentation and testing, we’ve found that the Qt5 debian container image provided by toradex is not ideal for our situation. This is mainly because it’s locked at Qt version 5.15.2, whereas we’ve recently transitioned to Qt version 6.5.2. As we hold a commercial license for Qt Device Creation, we wish to continue leveraging its benefits, including the Qt 6.5 LTS releases and Qt Device Utilities outlined here: Qt Device Utilities 6.4.0 | Qt Device Utilities 6.4.0.
Consequently, I have a specific inquiry:
Is it feasible to construct a custom Boot2Qt image using Yocto and subsequently run it within a Docker container in the Torizon environment?
I’ve already attempted to follow the instructions provided in this video tutorial: https://www.youtube.com/watch?v=_Y9mUT1Phi8&ab_channel=QtDayItalia. However, it seems that the content of the tutorial might be outdated. Could you provide guidance on an effective approach, potentially involving the use of Dockerfiles and docker-compose?