Hi @jrocher ,
Concerning the weston-vivante container, I started qt5-wayland-vivante:2 , it should also work right ? I think I actually also tried with the weston-vivante one and faced the exact same problem.
The applications inside qt5-wayland-vivante:2
should only work if weston-vivante:2
is up and running. Just to be sure, try doing the following:
-
Stop any running containers with
docker stop $(docker ps -a -q) && docker rm $(docker ps -a -q)
-
Start
weston-vivante:2
with this command:
docker run -e ACCEPT_FSL_EULA=1 -d --rm --name=weston --net=host --cap-add CAP_SYS_TTY_CONFIG \
-v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ \
--device-cgroup-rule='c 4:* rmw' --device-cgroup-rule='c 13:* rmw' \
--device-cgroup-rule='c 199:* rmw' --device-cgroup-rule='c 226:* rmw' \
torizon/weston-vivante:$CT_TAG_WESTON_VIVANTE --developer weston-launch \
--tty=/dev/tty7 --user=torizon
You should see a graphical desktop-like environment on your display after this command. If that’s not the case, then something is wrong with the Weston container and the QT apps will not work.
- Start the
qt5-wayland-vivante:2
container as you did before:
docker run -e ACCEPT_FSL_EULA=1 --rm -it --name=qt5 \
-v /tmp:/tmp \
-v /dev/dri:/dev/dri -v /dev/galcore:/dev/galcore \
--device-cgroup-rule='c 199:* rmw' --device-cgroup-rule='c 226:* rmw' \
torizon/qt5-wayland-examples-vivante:$CT_TAG_QT5_WAYLAND_EXAMPLES_VIVANTE \
bash
- Inside the container, try executing any of the sample applications:
/usr/lib/aarch64-linux-gnu/qt5/examples/quick/animation/animation &
Doing the steps above I was able to run the sample apps without any problems on a Colibri iMX8X with TorizonCore 5.7.0.
See if the error persists when doing the procedures mentioned above.
Best regards,
Lucas Akira