# AWS Spot instances for Integration-Testing Cookbooks on Github

**URL:** <https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859>\
**Category:** Chef Infra (archive)\
**Created:** [October 28, 2014, 7:24am UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859 "2014-10-28T07:24:30Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tknerr](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tknerr/32/21_2.png) [@tknerr](https://discourse.chef.io/u/tknerr)\
**Post date:** [October 28, 2014, 7:24am UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859/1 "2014-10-28T07:24:30Z")

</div>

Hi everybody,

having some cookbooks hosted on Github and using kitchen-ci for  
integration-testing them, I would like to have the kitchen-ci tests  
run on every commit / push.

With travis-ci (which I’m using for foodcritic / chefspec) this does  
not work unfortunately, since it prohibits creation of nested  
containers.

So I’m now considering to spin up an AWS spot instance during the  
travis-ci build to run the integration tests on.

Anyone doing this already?

Any pointers or suggestions to get me kick-started are heartily welcome 🙂

Cheers,  
Torben

---

<div class="post-metadata">

**Author:** ![tknerr](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tknerr/32/21_2.png) [@tknerr](https://discourse.chef.io/u/tknerr)\
**Post date:** [October 28, 2014, 7:32am UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859/2 "2014-10-28T07:32:43Z")

</div>

Weeeee, just found there is a kitchen-ec2 driver, and it has support for  
spot instances... neat! 🙂  
Am 28.10.2014 08:24 schrieb "Torben Knerr" [mail@tknerr.de](mailto:mail@tknerr.de):

> Hi everybody,
> 
> having some cookbooks hosted on Github and using kitchen-ci for  
> integration-testing them, I would like to have the kitchen-ci tests  
> run on every commit / push.
> 
> With travis-ci (which I'm using for foodcritic / chefspec) this does  
> not work unfortunately, since it prohibits creation of nested  
> containers.
> 
> So I'm now considering to spin up an AWS spot instance during the  
> travis-ci build to run the integration tests on.
> 
> Anyone doing this already?
> 
> Any pointers or suggestions to get me kick-started are heartily welcome 🙂
> 
> Cheers,  
> Torben

---

<div class="post-metadata">

**Author:** ![jeffbyrnes](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jeffbyrnes/32/1478_2.png) [@jeffbyrnes](https://discourse.chef.io/u/jeffbyrnes)\
**Post date:** [October 28, 2014, 10:35am UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859/3 "2014-10-28T10:35:25Z")

</div>

Torben,

We've been doing this with some of our cookbooks for the last few months, and in fact, have a talk on it at the Chef Boston meetup group in Sept.

Just getting going with my day right now; I'll follow-up this with more details & examples.

-- Jeff Byrnes

Lead DevOps Engineer

@thejeffbyrnes

> **[Homepage - Evertrue](https://www.evertrue.com/)**
>
> The Donor Experience Platform We are making the really hard job of fundraising so much easier for every fundraiser — so they can improve the experience of every donor. FIND OUT MORE EverTrue empowers your entire advancement organization Discover...

On Tue, Oct 28, 2014 at 3:25 AM, Torben Knerr [mail@tknerr.de](mailto:mail@tknerr.de) wrote:

> Hi everybody,  
> having some cookbooks hosted on Github and using kitchen-ci for  
> integration-testing them, I would like to have the kitchen-ci tests  
> run on every commit / push.  
> With travis-ci (which I'm using for foodcritic / chefspec) this does  
> not work unfortunately, since it prohibits creation of nested  
> containers.  
> So I'm now considering to spin up an AWS spot instance during the  
> travis-ci build to run the integration tests on.  
> Anyone doing this already?  
> Any pointers or suggestions to get me kick-started are heartily welcome 🙂  
> Cheers,  
> Torben

---

<div class="post-metadata">

**Author:** ![tknerr](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tknerr/32/21_2.png) [@tknerr](https://discourse.chef.io/u/tknerr)\
**Post date:** [October 28, 2014, 11:42am UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859/4 "2014-10-28T11:42:21Z")

</div>

Hi Jeff,

cool stuff, looking forward!

Cheers, Torben

On Tue, Oct 28, 2014 at 11:35 AM, Jeff Byrnes [jeff@evertrue.com](mailto:jeff@evertrue.com) wrote:

> Torben,
> 
> We've been doing this with some of our cookbooks for the last few months,  
> and in fact, have a talk on it at the Chef Boston meetup group in Sept.
> 
> Just getting going with my day right now; I'll follow-up this with more  
> details & examples.
> 
> --  
> Jeff Byrnes  
> Lead DevOps Engineer  
> @thejeffbyrnes  
> [http://www.evertrue.com](http://www.evertrue.com)
> 
> On Tue, Oct 28, 2014 at 3:25 AM, Torben Knerr [mail@tknerr.de](mailto:mail@tknerr.de) wrote:
> 
> > Hi everybody,
> > 
> > having some cookbooks hosted on Github and using kitchen-ci for  
> > integration-testing them, I would like to have the kitchen-ci tests  
> > run on every commit / push.
> > 
> > With travis-ci (which I'm using for foodcritic / chefspec) this does  
> > not work unfortunately, since it prohibits creation of nested  
> > containers.
> > 
> > So I'm now considering to spin up an AWS spot instance during the  
> > travis-ci build to run the integration tests on.
> > 
> > Anyone doing this already?
> > 
> > Any pointers or suggestions to get me kick-started are heartily welcome  
> > 🙂
> > 
> > Cheers,  
> > Torben

---

<div class="post-metadata">

**Author:** ![Tara\_Hernandez](https://avatars.discourse-cdn.com/v4/letter/t/ecccb3/32.png) [@Tara\_Hernandez](https://discourse.chef.io/u/Tara_Hernandez)\
**Post date:** [October 28, 2014, 4:27pm UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859/5 "2014-10-28T16:27:55Z")

</div>

Here’s a sample of kitchen files we use for ec2 provisioning, now that you’ve found that driver (we have wrapper automation that fills in those env vars, obviously)

driver:

name: ec2

ssh\_key: \<%= ENV[‘SSH\_KEY\_FILE’] %\>

aws\_ssh\_key\_id: \<%= ENV[‘AWS\_SSH\_KEY\_ID’] %\>

region: us-west-1

availability\_zone: \<%= ENV[‘AWS\_ZONE’] %\>

require\_chef\_omnibus: true

subnet\_id: \<%= ENV[‘AWS\_SUBNET’] %\>

security\_group\_ids: ‘\<%= ENV[‘AWS\_SEC\_GROUP’] %\>’

flavor\_id: ‘t1.micro’

provisioner:

name: chef\_solo

platforms:

- name: centos-6.4

suites:

- name: default

From: Torben Knerr \<[mail@tknerr.de](mailto:mail@tknerr.de)[mailto:mail@tknerr.de](mailto:mail@tknerr.de)\>  
Reply-To: "chef@lists.opscode.com[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)" \<[chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)\>  
Date: Tuesday, October 28, 2014 at 12:32 AM  
To: "chef@lists.opscode.com[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)" \<[chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)\>  
Subject: [chef] Re: AWS Spot instances for Integration-Testing Cookbooks on Github

Weeeee, just found there is a kitchen-ec2 driver, and it has support for spot instances… neat! 🙂

Am 28.10.2014 08:24 schrieb “Torben Knerr” \<[mail@tknerr.de](mailto:mail@tknerr.de)[mailto:mail@tknerr.de](mailto:mail@tknerr.de)\>:  
Hi everybody,

having some cookbooks hosted on Github and using kitchen-ci for  
integration-testing them, I would like to have the kitchen-ci tests  
run on every commit / push.

With travis-ci (which I’m using for foodcritic / chefspec) this does  
not work unfortunately, since it prohibits creation of nested  
containers.

So I’m now considering to spin up an AWS spot instance during the  
travis-ci build to run the integration tests on.

Anyone doing this already?

Any pointers or suggestions to get me kick-started are heartily welcome 🙂

Cheers,  
Torben

---

<div class="post-metadata">

**Author:** ![jeffbyrnes](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jeffbyrnes/32/1478_2.png) [@jeffbyrnes](https://discourse.chef.io/u/jeffbyrnes)\
**Post date:** [October 28, 2014, 5:12pm UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859/6 "2014-10-28T17:12:32Z")

</div>

Ok! Sorry this took so long to get back to. Here’s the slides from our presentation back in Sept: [http://evertrue.github.io/test-kitchen-travis-slides/](http://evertrue.github.io/test-kitchen-travis-slides/)

You can refer to these two cookbooks (one was done live during the preso) to guide you on how we set this up using EC2 & Travis:

> **[evertrue/et\_travis\_demo-cookbook](https://github.com/evertrue/et_travis_demo-cookbook)**
>
> et\_travis\_demo-cookbook - A cookbook to demonstrade how easy it is to set up Travis!

  

> **[evertrue/et\_travis\_live\_demo-cookbook](https://github.com/evertrue/et_travis_live_demo-cookbook)**
>
> et\_travis\_live\_demo-cookbook - Don't Break

  
Most pertinent is the .travis.yml & .kitchen.cloud.yml (which we force Test Kitchen to use by way of a Rake task).

Tara’s config, below, is very similar to ours, though clearly Jenkins-centric.

Bear in mind that kitchen-ec2, you’ll need to use the current HEAD of the Git repo (see this changeset for details on what’s missing from the current published release, v0.8.0). Hopefully they’ll cut a new version soon, but we use the bleeding edge version right now & it’s solid.

Tara, I’m curious, how did you get around the need for the AWS API keypair in your Test Kitchen config?

–  
Jeff Byrnes  
@berkleebassist  
Lead DevOps Engineer  
EverTrue  
704.516.4628

On October 28, 2014 at 12:28:13 PM, Tara Hernandez ([tara.hernandez@lithium.com](mailto:tara.hernandez@lithium.com)) wrote:

Here’s a sample of kitchen files we use for ec2 provisioning, now that you’ve found that driver (we have wrapper automation that fills in those env vars, obviously)

driver:  
name: ec2  
ssh\_key: \<%= ENV[‘SSH\_KEY\_FILE’] %\>  
aws\_ssh\_key\_id: \<%= ENV[‘AWS\_SSH\_KEY\_ID’] %\>  
region: us-west-1  
availability\_zone: \<%= ENV[‘AWS\_ZONE’] %\>  
require\_chef\_omnibus: true  
subnet\_id: \<%= ENV[‘AWS\_SUBNET’] %\>  
security\_group\_ids: ‘\<%= ENV[‘AWS\_SEC\_GROUP’] %\>'  
flavor\_id: ‘t1.micro’

provisioner:  
name: chef\_solo

platforms:

- name: centos-6.4

suites:

- name: default  
run\_list:
  - recipe[ci-jenkins::default]  
attributes: {  
“ci-jenkins”: {  
“enable\_cookbook\_testing”: true  
}  
}

From: Torben Knerr [mail@tknerr.de](mailto:mail@tknerr.de)  
Reply-To: "chef@lists.opscode.com" [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Date: Tuesday, October 28, 2014 at 12:32 AM  
To: "chef@lists.opscode.com" [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: AWS Spot instances for Integration-Testing Cookbooks on Github

Weeeee, just found there is a kitchen-ec2 driver, and it has support for spot instances… neat! 🙂

Am 28.10.2014 08:24 schrieb “Torben Knerr” [mail@tknerr.de](mailto:mail@tknerr.de):  
Hi everybody,

having some cookbooks hosted on Github and using kitchen-ci for  
integration-testing them, I would like to have the kitchen-ci tests  
run on every commit / push.

With travis-ci (which I’m using for foodcritic / chefspec) this does  
not work unfortunately, since it prohibits creation of nested  
containers.

So I’m now considering to spin up an AWS spot instance during the  
travis-ci build to run the integration tests on.

Anyone doing this already?

Any pointers or suggestions to get me kick-started are heartily welcome 🙂

Cheers,  
Torben

---

<div class="post-metadata">

**Author:** ![Tara\_Hernandez](https://avatars.discourse-cdn.com/v4/letter/t/ecccb3/32.png) [@Tara\_Hernandez](https://discourse.chef.io/u/Tara_Hernandez)\
**Post date:** [October 28, 2014, 5:38pm UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859/7 "2014-10-28T17:38:39Z")

</div>

Oh, sorry — the wrapper automation makes use of environment variables for that stuff (e.g. AWS\_SECRET\_KEY etc.) — it’s not needed in the driver definition and we try and keep that stuff at least slightly secure…

From: Jeff Byrnes \<[jeff@evertrue.com](mailto:jeff@evertrue.com)[mailto:jeff@evertrue.com](mailto:jeff@evertrue.com)\>  
Reply-To: "chef@lists.opscode.com[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)" \<[chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)\>  
Date: Tuesday, October 28, 2014 at 10:12 AM  
To: "chef@lists.opscode.com[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)" \<[chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)\>  
Subject: [chef] Re: Re: Re: AWS Spot instances for Integration-Testing Cookbooks on Github

Ok! Sorry this took so long to get back to. Here’s the slides from our presentation back in Sept: [http://evertrue.github.io/test-kitchen-travis-slides/](http://evertrue.github.io/test-kitchen-travis-slides/)

You can refer to these two cookbooks (one was done live during the preso) to guide you on how we set this up using EC2 & Travis:

- [https://github.com/evertrue/et\_travis\_demo-cookbook](https://github.com/evertrue/et_travis_demo-cookbook)
- [https://github.com/evertrue/et\_travis\_live\_demo-cookbook](https://github.com/evertrue/et_travis_live_demo-cookbook)

Most pertinent is the .travis.yml & .kitchen.cloud.yml (which we force Test Kitchen to use by way of a Rake task).

Tara’s config, below, is very similar to ours, though clearly Jenkins-centric.

Bear in mind that kitchen-ec2, you’ll need to use the current HEAD of the Git repo (see this changeset[https://github.com/test-kitchen/kitchen-ec2/compare/v0.8.0...master](https://github.com/test-kitchen/kitchen-ec2/compare/v0.8.0...master) for details on what’s missing from the current published release, v0.8.0). Hopefully they’ll cut a new version soon, but we use the bleeding edge version right now & it’s solid.

Tara, I’m curious, how did you get around the need for the AWS API keypair in your Test Kitchen config?

–  
Jeff Byrnes  
@berkleebassist[http://twitter.com/berkleebassist](http://twitter.com/berkleebassist)  
Lead DevOps Engineer  
EverTrue[http://www.evertrue.com/](http://www.evertrue.com/)  
704.516.4628

On October 28, 2014 at 12:28:13 PM, Tara Hernandez ([tara.hernandez@lithium.com](mailto:tara.hernandez@lithium.com)[mailto:tara.hernandez@lithium.com](mailto:tara.hernandez@lithium.com)) wrote:

Here’s a sample of kitchen files we use for ec2 provisioning, now that you’ve found that driver (we have wrapper automation that fills in those env vars, obviously)

driver:

name: ec2

ssh\_key: \<%= ENV[‘SSH\_KEY\_FILE’] %\>

aws\_ssh\_key\_id: \<%= ENV[‘AWS\_SSH\_KEY\_ID’] %\>

region: us-west-1

availability\_zone: \<%= ENV[‘AWS\_ZONE’] %\>

require\_chef\_omnibus: true

subnet\_id: \<%= ENV[‘AWS\_SUBNET’] %\>

security\_group\_ids: ‘\<%= ENV[‘AWS\_SEC\_GROUP’] %\>’

flavor\_id: ‘t1.micro’

provisioner:

name: chef\_solo

platforms:

- name: centos-6.4

suites:

- name: default

From: Torben Knerr \<[mail@tknerr.de](mailto:mail@tknerr.de)[mailto:mail@tknerr.de](mailto:mail@tknerr.de)\>  
Reply-To: "chef@lists.opscode.com[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)" \<[chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)\>  
Date: Tuesday, October 28, 2014 at 12:32 AM  
To: "chef@lists.opscode.com[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)" \<[chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)\>  
Subject: [chef] Re: AWS Spot instances for Integration-Testing Cookbooks on Github

Weeeee, just found there is a kitchen-ec2 driver, and it has support for spot instances… neat! 🙂

Am 28.10.2014 08:24 schrieb “Torben Knerr” \<[mail@tknerr.de](mailto:mail@tknerr.de)[mailto:mail@tknerr.de](mailto:mail@tknerr.de)\>:  
Hi everybody,

having some cookbooks hosted on Github and using kitchen-ci for  
integration-testing them, I would like to have the kitchen-ci tests  
run on every commit / push.

With travis-ci (which I’m using for foodcritic / chefspec) this does  
not work unfortunately, since it prohibits creation of nested  
containers.

So I’m now considering to spin up an AWS spot instance during the  
travis-ci build to run the integration tests on.

Anyone doing this already?

Any pointers or suggestions to get me kick-started are heartily welcome 🙂

Cheers,  
Torben

---

<div class="post-metadata">

**Author:** ![tknerr](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tknerr/32/21_2.png) [@tknerr](https://discourse.chef.io/u/tknerr)\
**Post date:** [October 29, 2014, 5:42am UTC](https://discourse.chef.io/t/aws-spot-instances-for-integration-testing-cookbooks-on-github/5859/8 "2014-10-29T05:42:36Z")

</div>

Thanks Jeff and Tara, exactly what I was looking for!

Cheers, Torben

On Tue, Oct 28, 2014 at 6:38 PM, Tara Hernandez  
[tara.hernandez@lithium.com](mailto:tara.hernandez@lithium.com) wrote:

> Oh, sorry — the wrapper automation makes use of environment variables for  
> that stuff (e.g. AWS\_SECRET\_KEY etc.) — it’s not needed in the driver  
> definition and we try and keep that stuff at least slightly secure…
> 
> From: Jeff Byrnes [jeff@evertrue.com](mailto:jeff@evertrue.com)  
> Reply-To: "[chef@lists.opscode.com](mailto:chef@lists.opscode.com)" [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> Date: Tuesday, October 28, 2014 at 10:12 AM  
> To: "[chef@lists.opscode.com](mailto:chef@lists.opscode.com)" [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> Subject: [chef] Re: Re: Re: AWS Spot instances for Integration-Testing  
> Cookbooks on Github
> 
> Ok! Sorry this took so long to get back to. Here’s the slides from our  
> presentation back in Sept:  
> [Test Kitchen & Travis CI](http://evertrue.github.io/test-kitchen-travis-slides/)
> 
> You can refer to these two cookbooks (one was done live during the preso) to  
> guide you on how we set this up using EC2 & Travis:
> 
> [GitHub - evertrue/et\_travis\_demo-cookbook: A cookbook to demonstrade how easy it is to set up Travis!](https://github.com/evertrue/et_travis_demo-cookbook)  
> [GitHub - evertrue/et\_travis\_live\_demo-cookbook: Don't Break](https://github.com/evertrue/et_travis_live_demo-cookbook)
> 
> Most pertinent is the .travis.yml & .kitchen.cloud.yml (which we force Test  
> Kitchen to use by way of a Rake task).
> 
> Tara’s config, below, is very similar to ours, though clearly  
> Jenkins-centric.
> 
> Bear in mind that kitchen-ec2, you’ll need to use the current HEAD of the  
> Git repo (see this changeset for details on what’s missing from the current  
> published release, v0.8.0). Hopefully they’ll cut a new version soon, but we  
> use the bleeding edge version right now & it’s solid.
> 
> Tara, I’m curious, how did you get around the need for the AWS API keypair  
> in your Test Kitchen config?
> 
> --  
> Jeff Byrnes  
> @berkleebassist  
> Lead DevOps Engineer  
> EverTrue  
> 704.516.4628
> 
> On October 28, 2014 at 12:28:13 PM, Tara Hernandez  
> ([tara.hernandez@lithium.com](mailto:tara.hernandez@lithium.com)) wrote:
> 
> Here’s a sample of kitchen files we use for ec2 provisioning, now that  
> you’ve found that driver (we have wrapper automation that fills in those env  
> vars, obviously)
> 
> driver:
> 
> name: ec2
> 
> ssh\_key: \<%= ENV['SSH\_KEY\_FILE'] %\>
> 
> aws\_ssh\_key\_id: \<%= ENV['AWS\_SSH\_KEY\_ID'] %\>
> 
> region: us-west-1
> 
> availability\_zone: \<%= ENV['AWS\_ZONE'] %\>
> 
> require\_chef\_omnibus: true
> 
> subnet\_id: \<%= ENV['AWS\_SUBNET'] %\>
> 
> security\_group\_ids: ‘\<%= ENV[‘AWS\_SEC\_GROUP'] %\>'
> 
> flavor\_id: 't1.micro'
> 
> provisioner:
> 
> name: chef\_solo
> 
> platforms:
> 
> - name: centos-6.4
> 
> suites:
> 
> - name: default
> 
> From: Torben Knerr [mail@tknerr.de](mailto:mail@tknerr.de)  
> Reply-To: "[chef@lists.opscode.com](mailto:chef@lists.opscode.com)" [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> Date: Tuesday, October 28, 2014 at 12:32 AM  
> To: "[chef@lists.opscode.com](mailto:chef@lists.opscode.com)" [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> Subject: [chef] Re: AWS Spot instances for Integration-Testing Cookbooks on  
> Github
> 
> Weeeee, just found there is a kitchen-ec2 driver, and it has support for  
> spot instances... neat! 🙂
> 
> Am 28.10.2014 08:24 schrieb "Torben Knerr" [mail@tknerr.de](mailto:mail@tknerr.de):
> 
> > Hi everybody,
> > 
> > having some cookbooks hosted on Github and using kitchen-ci for  
> > integration-testing them, I would like to have the kitchen-ci tests  
> > run on every commit / push.
> > 
> > With travis-ci (which I'm using for foodcritic / chefspec) this does  
> > not work unfortunately, since it prohibits creation of nested  
> > containers.
> > 
> > So I'm now considering to spin up an AWS spot instance during the  
> > travis-ci build to run the integration tests on.
> > 
> > Anyone doing this already?
> > 
> > Any pointers or suggestions to get me kick-started are heartily welcome  
> > 🙂
> > 
> > Cheers,  
> > Torben