Hacker News Reader

Well, Docker just slapped a "1.0" sticker on and called itself "production ready" when it clearly wasn't (features like in this 1.2 release are kind of mandatory for any serious deployments).

View on HN

You could already do these things outside of dockerland via the host-integration stuff (ie, systemd to handle restarts/monitoring).

1.0 was/is about API stability, engine stability, full ecosystem with Docker Hub, and enterprise support.

Yea, i really thought that this stuff should be out of dockerland. Not that i dislike the feature, just that it seems to overlap with established tools that excel at doing one thing well.

FWIW, now that docker is handling the restart/monitoring it can actually do it better than if systemd is doing it, since docker knows that it doesn't have to tear down and re-create the network namespace, unmount/remount the container's FS, etc.

So when a container is restarted via the restart policy, it not only happens faster, it will get the same IP as well.

> it will get the same IP as well.

Not for me. Just tested it.

How did you test it?

Reply on news.ycombinator.com