Greetings @Serghey
With regards to the 2 different displays with Weston let me explain. This is the command to launch the weston-vivante container from our Debian Containers for Torizon | Toradex Developer Center article.
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
If you run this command as is, you get the gray screen. If you run the command without the --developer flag you get the dark blue screen.
The difference is that this --developer flag decides which weston.ini config file is used. By default we ship 2 different weston.ini files with our containers. You can see the two different files here: debian-docker-images/weston-dev.ini at bullseye · toradex/debian-docker-images · GitHub
But anyways in short this explains the different graphical output you are seeing in Weston. Your docker-compose files don’t have the --developer switch so they should be using the dark blue screen. At least this is what I get when I run your compose files, I haven’t gotten the gray screen so far, so not sure what’s going on there. Perhaps you had other containers running?
Best Regards,
Jeremias