On a Jenkins Master-Slave configuration and need to run on the slaves Kitchen tests on several jobs. Kitchen for those who do not know it, runs infrastructure on demand using Vagrant and VirtualBox (in my case). Master and slave are both under Proxmox, so my questions is: is there a sane way to get running VirtualBox inside an OpenVZ container?, is there any workaround I can do to achieve this? I just don't want to create a physical node to run this kind of jobs.
VirtualBox – Running VirtualBox Under Proxmox
virtualboxvirtualization
Best Answer
As per my answer to this U&L Q&A titled: Can VirtualBox run under Xen Dom0? the answer here is no, you cannot run VM technologies such as this on top of XEN or Proxmox/OpenVZ. You can likely run OpenVZ within a VM inside of VirtualBox.
But I'm assuming you're asking your question mainly around the desire to allow Jenkins the ability to access more architectures.
KVM
What we do where I work is we setup multiple KVM instances of Linux (doesn't matter what distro) and on top of this run many VMs. You could do the same. This would be identical to using Vagrant + VirtualBox, so I'm not sure if that helps.
An alternative?
If you truly do not want to have to run this on physical hardware the 2 technologies that might allow you to do this are Docker and LXC. These are similar to Proxmox & OpenVZ, but allow for much more granular control. You still will not be running VirtualBox within these either, but perhaps you can conceive of a solution where you could leverage these 2 technologies instead.
excerpt LXC
excerpt Docker
Vagabond?
This might be another way out for you instead of utilizing Kitchen you could use Vagabond here instead. In looking at the website it claims to integrate with LXC (same technology mentioned above).
excerpt
Also according to the website it claims to have support with Kitchen 1.0.