There are attempts under the testimage-work branch to get bitbake -c testimage running in a container that lacks kvm and uses SLIRP instead of tun/tap. We need to get that working to enable a full build and test pipeline. While running containers in privileged mode might make things work, that seems less than ideal if we want to support multiple container runtimes and avoid security issues associated with privileged containers.
A better solution might be to use kubevirt to run a VM in the cluster as part of the pipeline...
There are attempts under the testimage-work branch to get
bitbake -c testimagerunning in a container that lacks kvm and uses SLIRP instead of tun/tap. We need to get that working to enable a full build and test pipeline. While running containers in privileged mode might make things work, that seems less than ideal if we want to support multiple container runtimes and avoid security issues associated with privileged containers.A better solution might be to use kubevirt to run a VM in the cluster as part of the pipeline...