News for hackers. Stuff that matters.
Re:Docker 1.2.0, with restart policies by troym on Friday August 22, 2014 @01:59PM (#8213180)
Maybe a bit off-topic.

I haven't found a satisfactory solution to having communicating containers across multiple hosts. There seems to be quite a few solutions in the making (libswarm, geard, etc). How are other people solving this (in production, beyond two or three hosts)?

Re:Docker 1.2.0, with restart policies by cpuguy83 on Friday August 22, 2014 @02:13PM (#8213240)
Re:Docker 1.2.0, with restart policies by troym on Friday August 22, 2014 @03:47PM (#8213618)
Interesting, thanks! FWIW, ambassadord has consul integration and that's something I've wanted.
Re:Docker 1.2.0, with restart policies by ivix on Friday August 22, 2014 @04:46PM (#8213862)
I simply expose ports (or do --net=host) and communicate between hosts in the normal fashion. Unless you don't trust your host I don't see the problem with that.
Re:Docker 1.2.0, with restart policies by Alupis on Friday August 22, 2014 @02:07PM (#8213217)
CoreOS seems to do what you are asking.