News for hackers. Stuff that matters.
Re:Docker 1.2.0, with restart policies by omglol on Friday August 22, 2014 @02:10PM (#8213229)
Well, Docker just slapped a "1.0" sticker on and called itself "production ready" when it clearly wasn't (features like in this 1.2 release are kind of mandatory for any serious deployments).
Re:Docker 1.2.0, with restart policies by cpuguy83 on Friday August 22, 2014 @02:33PM (#8213327)
You could already do these things outside of dockerland via the host-integration stuff (ie, systemd to handle restarts/monitoring).

1.0 was/is about API stability, engine stability, full ecosystem with Docker Hub, and enterprise support.

Re:Docker 1.2.0, with restart policies by fidlefodl on Friday August 22, 2014 @03:35PM (#8213565)
Yea, i really thought that this stuff should be out of dockerland. Not that i dislike the feature, just that it seems to overlap with established tools that excel at doing one thing well.
Re:Docker 1.2.0, with restart policies by cpuguy83 on Friday August 22, 2014 @04:41PM (#8213839)
FWIW, now that docker is handling the restart/monitoring it can actually do it better than if systemd is doing it, since docker knows that it doesn't have to tear down and re-create the network namespace, unmount/remount the container's FS, etc.

So when a container is restarted via the restart policy, it not only happens faster, it will get the same IP as well.

Re:Docker 1.2.0, with restart policies by mattes on Monday August 25, 2014 @01:58PM (#8222980)
> it will get the same IP as well.

Not for me. Just tested it.

Re:Docker 1.2.0, with restart policies by cpuguy83 on Tuesday August 26, 2014 @01:01PM (#8228255)
How did you test it?