Hi all, no World-changing features in this one, but we believe that over time, relentless incremental improvements can make a huge difference.<p>This week we are freezing all feature merges and focusing on refactoring, code cleanup and generally repaying as much technical debt as possible.<p>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.
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.<p>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.<p>[0]: <a href="http://serverfault.com/a/620513/85897" rel="nofollow">http://serverfault.com/a/620513/85897</a><p>[1]: <a href="https://coreos.com/blog/stable-release/" rel="nofollow">https://coreos.com/blog/stable-release/</a>
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.<p>While great, I worry that this is a part-solution that will delay the implementation of a proper one.
Maybe a bit off-topic.<p>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)?
Any update on when the OS X version will be available? I'm only seeing version 1.1.2 here:<p><a href="https://github.com/boot2docker/osx-installer/releases" rel="nofollow">https://github.com/boot2docker/osx-installer/releases</a>
Oh this is juuuust great. /sarcasm.<p>So now docker is taking on the work of what systemd and other daemon-managers are supposed to solve? Looking forward to docker run --restart on-failure ubuntu /bin/bash exit -1<p>When you include a --restart "feature" you know for sure you have don goofed.<p>But anyway, the rest of the stuff looks like pure candy. Great job!
How to deal with persistent storage (e.g. databases) in Docker 1.2?<p>is this info up-to-date? <a href="http://stackoverflow.com/questions/18496940/how-to-deal-with-persistent-storage-e-g-databases-in-docker" rel="nofollow">http://stackoverflow.com/questions/18496940/how-to-deal-with...</a>