In you're interested, we also announced beta versions of Swarm and Compose today:<p><a href="http://blog.docker.com/2015/02/scaling-docker-with-swarm/" rel="nofollow">http://blog.docker.com/2015/02/scaling-docker-with-swarm/</a><p><a href="http://blog.docker.com/2015/02/announcing-docker-compose/" rel="nofollow">http://blog.docker.com/2015/02/announcing-docker-compose/</a><p>And a sneak preview of how these tools can work together:<p><a href="http://blog.docker.com/2015/02/orchestrating-docker-with-machine-swarm-and-compose/" rel="nofollow">http://blog.docker.com/2015/02/orchestrating-docker-with-mac...</a>
It looks interesting but seems like a very Docker-centric Packer[0] in that it has code to create ready to go with Docker images on various cloud providers and virtual machines.<p>The real hurdle and problems you'll be solving with Docker are when you have containers on separate hosts. Will Machine handle configuring firewalls, SSL, SSH keys and all that jazz across hosts so containers can reach each other? I've automated a lot of this myself but would love something that does it for you (other than the existing discovery service tools that often introduce problems of their own). From the post it seems like Machine will also handle this but I wonder how and how well.<p>[0] - <a href="https://packer.io/" rel="nofollow">https://packer.io/</a>
This looks pretty interesting. Could someone give me a good use-case for this? I suppose spinning up dev environment on a host other than localhost could be useful? I could also see this being useful as an interface for multiple docker-installed production environments.<p>Perhaps someone could give me a "for instance."
This looks like an interesting project. I'd have to spend some time with it to determine if it would suit my deployment needs. I wrote a tool to help with docker deployment <a href="https://github.com/mrinterweb/freighter" rel="nofollow">https://github.com/mrinterweb/freighter</a>.
I didn't see a clear "Read the Documentation here" link on the article. That's a bit disappointing.<p>Here's what I found with a quick search on Google: <a href="https://docs.docker.com/machine/" rel="nofollow">https://docs.docker.com/machine/</a>
That sounds like a Docker-only competitor to Vagrant: it would be interesting to have a direct features comparaison because Vagrant is already pretty handy, even with Docker boxes.