Sorry to take so long.
You can get X11 to run on target despite all attempts to lock it down.
Helps if one edits this
sudo cat /var/sota/storage/docker-compose/docker-compose.yml
so it looks like this
services:
weston:
cap_add:
- CAP_SYS_TTY_CONFIG
container_name: App_weston
device_cgroup_rules:
- c 4:0 rmw
- c 4:7 rmw
- c 13:* rmw
- c 199:* rmw
- c 226:* rmw
environment:
ACCEPT_FSL_EULA: '1'
image: torizon/weston-vivante@sha256:b39bd723e554a95522bd6774796d6af7cac7cf4960e1c142b9a6f45e62691f45
network_mode: host
volumes:
- source: /tmp
target: /tmp
type: bind
- source: /dev
target: /dev
type: bind
- source: /run/udev
target: /run/udev
type: bind
version: '2.4'
Then cold boot first.
docker pull seasonedgeek/xclock-demo
docker run --rm -d -v /tmp:/tmp -v /var/run/dbus:/var/run/dbus -v /dev/galcore:/dev/galcore --device-cgroup-rule='c 199:* rmw' seasonedgeek/xclock-demo
There is also this demo container for NanoGUI
docker pull seasonedgeek/base_build_container
docker run --rm -it -v /tmp:/tmp -v /var/run/dbus:/var/run/dbus -v /dev/galcore:/dev/galcore --device-cgroup-rule='c 199:* rmw' seasonedgeek/base_build_container /bin/sh
su torizon
export DISPLAY=:0
export XDG_RUNTIME_DIR=/tmp/1000-runtime-dir
example1
Sorry, image too big to upload