News for hackers. Stuff that matters.
Re:Docker 1.2.0, with restart policies by IanCal on Friday August 22, 2014 @08:57PM (#8214614)
I'm not sure about how I feel about this (edit - restart policies). It's cool, but seems to ignore what the OTP part of erlang development learned. They've already gone to "X number of restarts = failure" but with no time involved. There's also no hierarchy, which is where you really start to get the benefits.

While great, I worry that this is a part-solution that will delay the implementation of a proper one.

Re:Docker 1.2.0, with restart policies by michaelneale on Saturday August 23, 2014 @03:33AM (#8215266)
You can happily use containers supervised by systemd in a hierarchy like any other process if you like.
Re:Docker 1.2.0, with restart policies by cpuguy83 on Monday August 25, 2014 @12:24PM (#8222438)
1) We do degrade restarts over time. 2) There is hierarchy (so it will start linked containers).
Re:Docker 1.2.0, with restart policies by IanCal on Monday August 25, 2014 @02:47PM (#8223346)
Perhaps I'm being a bit harsh.

> 1) We do degrade restarts over time.

Is this adjustable? X restarts in Y seconds? I feel this is something that could be quite application specific.

> 2) There is hierarchy (so it will start linked containers).

So if A has a link to B, will A be restarted if B is restarted?

I'd be aiming to build hierarchies with restart strategies like these:

http://www.erlang.org/doc/design_principles/sup_princ.html

Re:Docker 1.2.0, with restart policies by cpuguy83 on Wednesday August 27, 2014 @03:50PM (#8234368)
1) I know you can specify the number of restarts, not sure yo can specify the gradual decay of the restarts

2) No, this is not the goal of the restart policies. I think this would be best implemented by something watching the docker event stream.