A container image that is able to run bitbake/poky. It has helpers to create users and groups within the container. This is so that the output generated in the container will be readable by the user on the host.
Here is a way I've used to get graphical qemu output using the publicvnc argument with runqemu.
Forward the vnc port when you start the container. Using docker run, add -p 5900:5900 to the command line. For example:
docker run -p 5900:5900 ...
Setup your build environment as normal.
Start qemu using runqemu and use the publicvnc argument.
pokyuser@241af804767d:/build$ runqemu slirp publicvnc core-image-sato
Outside of the container on the host, use a vnc client to connect to the vncserver that was started by qemu. For example:
~% vncviewer -FullColor localhost:5900
You could also start a vncserver manually inside the container rather than using the one builtin to qemu. But if these instructions work for you, I don't want to overload you with options.
Hi @fengjinyuan,
Here is a way I've used to get graphical qemu output using the publicvnc argument with runqemu.
Forward the vnc port when you start the container. Using docker run, add -p 5900:5900 to the command line. For example:
docker run -p 5900:5900 ...
Setup your build environment as normal.
Start qemu using runqemu and use the publicvnc argument.
pokyuser@241af804767d:/build$ runqemu slirp publicvnc core-image-sato
Outside of the container on the host, use a vnc client to connect to the vncserver that was started by qemu. For example:
~% vncviewer -FullColor localhost:5900
You could also start a vncserver manually inside the container rather than using the one builtin to qemu. But if these instructions work for you, I don't want to overload you with options.