This initial configuration uses kitchen-vagrant to test the tools cookbook.
I tried, and failed^Whaven't yet succeeded in getting more complex cookbooks to run, so I fell back on a pretty simple cookbook. Even then, there were challenges getting it to work with kitchen-docker, so I stuck with kitchen-vagrant for now.
The choice of a global test-kitchen setup vs a per-cookbook setup is not my first preference. Unfortunately there's no straightforward way to implement anything else, given our mono-repo and not using any cookbook publication systems. Using a global test-kitchen config is also the result that @zerebubuth came up with independently during work in June.
Oh, I should note that the "testing" of the tools cookbook only goes as far as the recipe converging successfully, it doesn't yet have any serverspec-based verification.
Hmm, so this seems to want to use virtualbox which is something that is not getting anywhere near my machine... Not sure if it is explicitly requesting that somehow or not, as I thought I had vagrant using libvirt...
Ah you need to set VAGRANT_DEFAULT_PROVIDER=libvirt but then you find that the bento/ubuntu-16.04 box doesn't support the libvirt provider!
It's possible to override configuration using a .kitchen.local.yml file, if that's useful.
That should allow setting the driver provider, and will hopefully allow you to choose a different image.
Yes I've managed to get it working now with the peru/ubuntu-16.04-server-amd64 box.
It's pretty slow mind - abut 3 minutes to run that one test on my machine.
Just for the record this .kitchen.local.yml worked for me:
- name: ubuntu-16.04