Yeah, the Vagrant + Docker use case is how I'm using it. This is the flow that I'm pushing my company to use:
* CoreOS/Vagrant
* Docker containers with basic infrastructure (eg LAMP/Ruby+Postgres)
* Containers 'forked' for each client (and company project)
* Central container repo for the team to use
As soon as CoreOS is ready for production we're going to look at using it for deployment.
We might not be using it 100% correctly, but so far it's nothing short of amazing. The basic 'git for OS' flow I get out if it makes me smile every time. Dockerfiles are way, way, way easier than Chef, Puppet or Ansibke, and the central repo is a synch to picture and imagine in comparison.
So, you're not running Docker in production at this point?
Are you putting the whole stack in one big container and running one container per Vagrant VM? Or are you spreading a client stack across multiple containers?
* CoreOS/Vagrant
* Docker containers with basic infrastructure (eg LAMP/Ruby+Postgres)
* Containers 'forked' for each client (and company project)
* Central container repo for the team to use
As soon as CoreOS is ready for production we're going to look at using it for deployment.
We might not be using it 100% correctly, but so far it's nothing short of amazing. The basic 'git for OS' flow I get out if it makes me smile every time. Dockerfiles are way, way, way easier than Chef, Puppet or Ansibke, and the central repo is a synch to picture and imagine in comparison.