TL;DR:
.kitchen.yml 1
2
3
4
5
6
7
8
9
10
11
# .kitchen.yml
---
driver :
name : docker
use_sudo : false # this depends if you need to do `sudo` to run `docker` command or not
disable_upstart : false
image : ubuntu-upstart:14.04
run_command : /sbin/init
platforms :
- name : ubuntu-14.04
It is possible because there is this official base image specifically for upstart: https://registry.hub.docker.com/_/ubuntu-upstart/.
After making your .kitchen.yml
look like this, just use kitchen
as you would normally would.
Happy coding! @tdd_fellow on twitter .
Alex has been developing software for the past 20+ years, out of which, 12+ commercially. He has worked for a diverse variety of businesses: early-stage and late-stage start-ups, established product companies, agencies, and consultancies; and in a variety of industries: education, accounting, housing, online marketplaces, automotive, fintech, blockchain, privacy, online marketing, productivity, cloud, and design. He has given tech and inspirational talks at international conferences and local meet-ups since 2015. Alex has spent a significant chunk of his time coaching software developers, engineering managers, and start-up CTOs. He has written production code in 20 programming languages on the back-end, front-end, native mobile, and desktop. Alex cares the most about software industry, professionalism, quality, and well-being of developers.
Aug 5 th , 2015 7:10 pm
chef , docker , kitchen-docker , ruby , test-kitchen , ubuntu , upstart
« Using contracts.ruby with RSpec
Docker Machine guide (VirtualBox on Mac OS X) »