Vagrant with Docker: How to set up Postgres, Elasticsearch and Redis on Mac OS X | Hacker News Reader

Vagrant with Docker: How to set up Postgres, Elasticsearch and Redis on Mac OS X

maori.geek.nz

66 pointsgrahar6422 comments

I have done something similar to this with a MEAN stack where I boot docker containers inside a single vagrant vm that is provisioned with shell scripts. The containers then have their ports exposed to vagrant up to my localhost so I can interact with each container individually. I should write a blog post about this soon.

I would love to see your Vagrantfile! I have a similar need, but can't figure it out :(

> I cannot yet see where this "Vagrant with Docker" path is going. However, after seeing what is possible I cannot help but think about how else it can be used. Plus, it is the most fun I have ever had with virtualisation, and fun is what programming is all about.

For me the biggest benefit is being able to have a developer workstation setup in minutes that (more-or-less) mirrors the production environment. This has big benefits for simplifying development setup as well as making testing more realistic.

Have you looked into Fig? (http://orchardup.github.io/fig/)

I use it to accomplish something very similar, standardized dev environments on OS X through docker containers.

Edit: I should probably add that my dev environment also relies on containers running both Postgres and Redis.

Hey, so what is the difference between my setup and figs? I assume it is just that all the port forwarding and folder stuff from the virtual machine is made easier?

That's pretty much it. Just two different approaches to the same thing. I use docker-osx (https://github.com/noplay/docker-osx) instead of boot2loader. Didn't run into any weird virtualization issues with it.

The format for the fig.yml file is even very similar to that of your VagrantFile (https://gist.github.com/ChrisChares/66916dd6dc0d5828520a)

If you have the time, could you please review our docker + fig instructions? These instructions are for Quill.org, a web app that provides free writing activities to middle school and high school students.

https://github.com/empirical-org/Documentation/blob/master/G...

We are a non-profit, open source community, and we recently set up our dev environment in Docker to encourage OSS contributions. We may be missing a few crucial pieces of instruction for developers unfamiliar with Docker, such as killing docker images once a developer is finished working on a project.

You can reach me at peter at quill.org

Sent you an email

As someone who uses brew versions of postgres, elasticsearch and redis, what benefit would I get moving to a setup like this?

Possibility to break things, use multiple versions at the same time, testing dangerous operations, seamless deployments, etc.

Multiple versions at once is a big sell for me. At the moment I have 3 different MySQL installs to handle different work and side projects. With vagrant, this is practically trivial to maintain.

If you have multiple people on your team, a common dev environment can be a huge time-saver. New developers can install an identical environment quickly.

Another benefit is that your project's development environment is self-contained. It's not going to clash with anything else on your system, and will even work across platforms.