Docker 1.2.0, with restart policies

#1

Post by julien421 » Fri, Aug 22, 2014, 5:03 PM UTC

Docker 1.2.0, with restart policies
blog.docker.com

Re: Docker 1.2.0, with restart policies

#2

Post by waffle_ss » Fri, Aug 22, 2014, 5:20 PM UTC

This is excellent news. The lack of a container restart policy was the main reason why I was spending a bunch of time learning CoreOS and fleet.

Trying to get CoreOS installed on VPS providers is a huge pain[0], and fleet and etcd are technically not labelled as production-ready (only CoreOS used as a base OS is)[1], so I'm really glad I can go back to vanilla Docker.

[0]: http://serverfault.com/a/620513/85897

[1]: https://coreos.com/blog/stable-release/

Re: Docker 1.2.0, with restart policies

#3

Post by shykes » Fri, Aug 22, 2014, 5:34 PM UTC

Hi all, no World-changing features in this one, but we believe that over time, relentless incremental improvements can make a huge difference.

This week we are freezing all feature merges and focusing on refactoring, code cleanup and generally repaying as much technical debt as possible.

We are also considering a gradual slowdown of the release cadence (we currently cut a release every month), to give more time for QA. Even though we work hard to keep master releasable at all times and run every merge through the full test suite, in practice there can never be enough real-world testing before a release. An 8-week cycle (which is roughly what Linux does) would allow us to freeze the release 1-2 weeks in advance and do more aggressive QA.

Re: Docker 1.2.0, with restart policies

#4

Post by jijojv » Fri, Aug 22, 2014, 5:44 PM UTC

Writable `/etc/hosts`, `/etc/resolv.conf` is huge - no more local dns hacks.

Re: Docker 1.2.0, with restart policies

#5

Post by shykes » Fri, Aug 22, 2014, 5:45 PM UTC

jijojv wrote: post #4

Writable `/etc/hosts`, `/etc/resolv.conf` is huge - no more local dns hacks.

Yeah that one was super-high on the request list, there were 3 competing patches before we finally got it right.

Re: Docker 1.2.0, with restart policies

#6

Post by nathankleyn » Fri, Aug 22, 2014, 5:48 PM UTC

shykes wrote: post #3

Hi all, no World-changing features in this one, but we believe that over time, relentless incremental improvements can make a huge difference. This week we are freezing all feature merges and focusing on refactoring, code cleanup and generally repaying as much technical debt as possible. We are also considering a gradual slowdown of the release cadence (we currently cut a release every month), to give more time for Q…

You guys are doing a fantastic job, anything that can give you a bit more of a breather between releases and increase quality is something I'm certain the community will embrace.

Re: Docker 1.2.0, with restart policies

#7

Post by omglol » Fri, Aug 22, 2014, 5:49 PM UTC

shykes wrote: post #3

Hi all, no World-changing features in this one, but we believe that over time, relentless incremental improvements can make a huge difference. This week we are freezing all feature merges and focusing on refactoring, code cleanup and generally repaying as much technical debt as possible. We are also considering a gradual slowdown of the release cadence (we currently cut a release every month), to give more time for Q…

This seems to be the real 1.0 release...

Re: Docker 1.2.0, with restart policies

#8

Post by [deleted] » Fri, Aug 22, 2014, 5:50 PM UTC

waffle_ss wrote: post #2

This is excellent news. The lack of a container restart policy was the main reason why I was spending a bunch of time learning CoreOS and fleet. Trying to get CoreOS installed on VPS providers is a huge pain[0], and fleet and etcd are technically not labelled as production-ready (only CoreOS used as a base OS is)[1], so I'm really glad I can go back to vanilla Docker. [0]: http://serverfault.com/a/620513/85897 [1]: h…

[deleted]

Re: Docker 1.2.0, with restart policies

#9

Post by [deleted] » Fri, Aug 22, 2014, 5:51 PM UTC

waffle_ss wrote: post #2

This is excellent news. The lack of a container restart policy was the main reason why I was spending a bunch of time learning CoreOS and fleet. Trying to get CoreOS installed on VPS providers is a huge pain[0], and fleet and etcd are technically not labelled as production-ready (only CoreOS used as a base OS is)[1], so I'm really glad I can go back to vanilla Docker. [0]: http://serverfault.com/a/620513/85897 [1]: h…

[deleted]

Re: Docker 1.2.0, with restart policies

#10

Post by Alupis » Fri, Aug 22, 2014, 5:52 PM UTC

waffle_ss wrote: post #2

This is excellent news. The lack of a container restart policy was the main reason why I was spending a bunch of time learning CoreOS and fleet. Trying to get CoreOS installed on VPS providers is a huge pain[0], and fleet and etcd are technically not labelled as production-ready (only CoreOS used as a base OS is)[1], so I'm really glad I can go back to vanilla Docker. [0]: http://serverfault.com/a/620513/85897 [1]: h…

> I was wasting a bunch of time learning CoreOS

I'm pretty sure CoreOS and Docker are different solutions to different problems. So... one is not really inter-changeable with another, and thus you were not "wasting" your time.

So, perhaps you didn't understand the problem you were trying to solve? Docker is about application environment isolation/portability (not! virtualization! -- there is no security provided here), where CoreOS is about scaling and HA.