+1 on what rvs says. Vagrant seems to be a useful tool for operating system unable to perform real work (no need to list them - we all know their names). In the CI and, I presume most common dev environments, it just makes sense to run native hypervisor, without going through the huge VirtualBox PITA.
Cos On Tue, Aug 19, 2014 at 10:38AM, Roman Shaposhnik wrote: > On Tue, Aug 19, 2014 at 7:25 AM, Jay Vyas <[email protected]> wrote: > > Hi bigtop. > > > > I've been using vagrant to build and spin up docker containers /run tasks. > > Same here. Vagrant running CoreOS + Docker is my personal workflow > these days. > > > It's really convenient because it does stuff like ssh/ destroy/ share > > folders > > (so the build artifact is available), etc for you..and is portable (it runs > > even > > on windows or mac, by spinning up a lightweight lxc vm). > > > > Do we want to consider that as the way we do the dockerized ci ? > > If so just point me to some patches and I can try to pitch in on the docker > > infrastructure efforts in that capacity if so. > > Docker is very much coming in. Not sure about Vagrant. Frankly the only > reason I use it is because I'm stuck with a laptop incapable of running > a real operating system well. On our slaves, though, we can simply run > Docker natively. Not sure what the value of Vagrant would be. > > Thanks, > Roman.
