Are you kidding?. Ability to modify /etc/hosts and specifying exact Capabilities is awesome. Thanks for the great work. I for one waited very long for this :)
Re:Docker 1.2.0, with restart policies
by simonebrunozzi on Friday August 22, 2014 @02:31PM
(#8213323)
Hi Solomon! I agree with prudhvis here - I think this is quite a nice add!
Keep up the good work!
Now that needs to be possible in docker build:
https://github.com/docker/docker/issues/1916
That said, yes this release looks interesting!
Glad I'm not the only one. I maintain an embedded system and a bunch of its apps - at every point in the Docker file where mknod & friends must do their thing, I have to cut the Dockerfile right there and do docker run --privileged for that build step... and so on.
It hasn't bothered me enough to comment on that issue though, Docker has really improved my workflow enormously.
Re:Docker 1.2.0, with restart policies
by nathankleyn on Friday August 22, 2014 @01:48PM
(#8213138)
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
by hipsters_unite on Friday August 22, 2014 @08:26PM
(#8214542)
I've spent literally the last week working out restart strategies for our critical containers, so it's fair to say this has something pretty world-changing as I might be able to ship next week now. Seriously, I was writing bash wrappers to listen for exit codes and all sorts to make my own pseudo exit hooks on the host, so this is just awesome.
Thanks guys!
I literally needed writable /etc/resolv.conf just this morning. You couldn't have timed the release any better.
Re:Docker 1.2.0, with restart policies
by tlrobinson on Friday August 22, 2014 @03:11PM
(#8213486)
ravenkat: in case you see this, it looks like you've been hellbanned. Since your question was a reasonable one, I'll copy it here:
"Currently if we restart docker daemon, all the running containers also restart. Are there any plans to keep the running containers running even if we upgrade our docker daemon?"
Definitely a reasonable question.
The answer is yes, there are plans to do exactly that :)
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.