10528 2016-10-28 18:59:54 +0000 Add VNC support for cli containers for QEMU 2025-10-23 15:24:37 +0000 1 1 6 Yocto Project Subprojects CROPS crops-default 2.3 x86 Multiple RESOLVED FIXED Medium enhancement 5.99 9592 1 brian.avery unassigned jose.perez.carranza libertad.gonzalez.de.la.cruz randy.macleod ross.burton tim.orling --- --- Yes (doc changes required) oldest_to_newest 67736 0 brian.avery 2016-10-28 18:59:54 +0000 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. 72887 1 brian.avery 2017-04-27 07:16:15 +0000 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. 75460 2 brian.avery 2017-07-30 13:31:52 +0000 Moving to M3 76174 3 brian.avery 2017-08-25 22:07:42 +0000 to M4 78621 4 brian.avery 2017-12-08 21:54:04 +0000 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 79863 5 chin.huat.ang 2018-03-19 22:51:15 +0000 runqemu publicvnc option works for me too, I'm able to connect to qemu's VNC display after mapping -p 5900:5900 96896 6 randy.macleod 2023-10-24 14:24:39 +0000 Bulk move from 4.99 or 0.00 to 5.99 103054 7 ross.burton 2025-10-23 15:24:37 +0000 Fixed in crops, eg https://github.com/crops/yocto-dockerfiles/commit/89280d8d3368282d8362723d328b397225bf7d41.