The current containers need to have a vnc session available so that we an connect a vnc client to them and so that things like $DISPLAY=42:0 qemu can run and we can connect to the container using a vnc client. Running such a container you would need to map the vnc port aka -p 6900:5900 for example and then you can connect to the container x display.
Demoting this to a medium+. It's not a part of YP so much as part of a derivative project (CROPS). Since HIGH bugs should be release blockers for YP or candidates for release blockers, having CROPS bugs be HIGH just get's confusing.
Moving to M3
to M4
Moving to Joshua. The PR to implement this is on github. The test to verify it works is not. A test could look something like: virtualenv FROG . FROG/bin/activate pip install vncdotool vncdo -s 192.168.168.88 -p "" capture screen.png identify -unique -verbose screen.png | egrep lime assuming that we ran a clock with a green background. $>xclock -bg green
runqemu publicvnc option works for me too, I'm able to connect to qemu's VNC display after mapping -p 5900:5900
Bulk move from 4.99 or 0.00 to 5.99
Fixed in crops, eg https://github.com/crops/yocto-dockerfiles/commit/89280d8d3368282d8362723d328b397225bf7d41.