3 ms·

I run several processes on each VM, each in their own container, and use Docker links which exposes environment variables into each container describing ip/port

I run several processes on each VM, each in their own container, and use Docker links which exposes environment variables into each container describing ip/port information for dependent services. It was really easy and works great. Furthermore, you can easily set all of the containers to share the same networking namespace so they can all just listen locally if you wanted a turn key solution. The pretty trivial issue of single-host service discovery is not a very strong argument against the benefits of single process containers in my experience.

opendais 12y ago
In order to do things your way you need: 1) Multiple docker containers to spin up and be managed. 2) Multiple health checks. 3) Set additional flags/do additional config for Docker. The fact people consistently say "Eh, this is a non-issue" is great. It means you are much luckier and more skilled than I since you can manage all of that with 0 additional effort. For me, all of this is effort I don't need to expend.