Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker 1.2.0, with restart policies

blog.docker.com

Post reply on HN
Print view View original

51–60 of 76 posts

Re: Docker 1.2.0, with restart policies

#51

Post by antocv »

Oh this is juuuust great. /sarcasm.

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

When you include a --restart "feature" you know for sure you have don goofed.

But anyway, the rest of the stuff looks like pure candy. Great job!

Re: Docker 1.2.0, with restart policies

#52

Post by knickle »

antocv wrote: post #51

Oh this is juuuust great. /sarcasm. 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 When you include a --restart "feature" you know for sure you have don goofed. But anyway, the rest of the stuff looks like pure candy. Great job!

1) Then don't use it in your scripts.

2) Restart policies are exposed in the API, so daemon managers can leverage this feature to hook in their own restart policies in a consistent, supported way.

Re: Docker 1.2.0, with restart policies

#53

Post by darklajid »

prudhvis wrote: post #16
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…

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 :)

Now that needs to be possible in docker build:

https://github.com/docker/docker/issues/1916

That said, yes this release looks interesting!

Re: Docker 1.2.0, with restart policies

#54

Post by shykes »

namin wrote: post #49
justizin wrote: post #30

Earlier quoted context omitted.

Use the Vagrant env, boot2docker is a mess IMO.

I liked the Vagrant env but I don't see it mentioned as an option here: https://docs.docker.com/installation/#installation Are there any up-to-date installation instructions for the Vagrant env?

It's no longer supported. I use the standard Mac setup (boot2docker + Virtualbox) and it works quite well for me. It's my primary environment for developing Docker :)

Re: Docker 1.2.0, with restart policies

#55

Post by sciurus »

antocv wrote: post #51

Oh this is juuuust great. /sarcasm. 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 When you include a --restart "feature" you know for sure you have don goofed. But anyway, the rest of the stuff looks like pure candy. Great job!

There's definitely feature overlap, and there are still problems running docker via systemd as show by the existence of workarounds like https://github.com/ibuildthecloud/systemd-docker

Re: Docker 1.2.0, with restart policies

#57

Post by hipsters_unite »

frik wrote: post #27

How to deal with persistent storage (e.g. databases) in Docker 1.2? is this info up-to-date? http://stackoverflow.com/questions/18496940/how-to-deal-with...

Mountable volumes and data containers works for us in staging atm, you can easily spin up single task dockers to pull that out, tar it up and send to S3 as a backup regime as well.

Re: Docker 1.2.0, with restart policies

#58

Post by hipsters_unite »

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…

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!

Re: Docker 1.2.0, with restart policies

#59

Post by csirac2 »

darklajid wrote: post #53
prudhvis wrote: post #16

Earlier quoted context omitted.

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 :)

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

#60

Post by IanCal »

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.

Post reply on HN