I use Docker in my dev environment. Points being:

1. You dev machine doesn’t need to have dependencies other than Docker
2. With Docker Compose I can easily grasp what other services (DBs, whatnots) that my app needs.
3. I use OSX and most likely will need to deploy to Linux servers, so I use containers to build releases.

My first project (a Phoenix API) used Docker for deployment too, simply because the rest of the project was using it (and the ops team asked me to). As I watch and read many materials about Elixir, Erlang, and OTP, I have doubts; seems to me that Erlang/OTP provides many distribution and fault tolerance features that doesn’t play well if we’re using Docker (mainly because, yeah, the networking).

But I think I still wouldn’t dump Docker for my dev env It’s so cheaper than VMs.

I use it for my blog, and we use it at work. I like that I can neatly separate build-time and run-time dependencies, and manage server setups. I also like that I can get something very similar to production on my dev machine. The ability to start multiple instances of the same image also works nicely for us, allowing each member of the team to have their own private deployment of production on the same server. We could do it without containers, but it’s quite simple with docker run.

I’m personally not much of a fan of elaborate ecosystem around Docker, such as CoreOS or Kubernetes. It feels to me as a quite complex emulation of what Erlang can handle directly.

[quote=“sasajuric, post:5, topic:2513”]
I’m personally not much of a fan of elaborate ecosystem around Docker, such as CoreOS or Kubernetes. It feels to me as a quite complex emulation of what Erlang can handle directly.
[/quote] X 100 looking at startups wasting resources deploying super elaborate systems around k8s, mesos, terraform is maddening