Live data from Hacker News

Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

blog.docker.com

11–20 of 80 posts

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#11
What's the relation between Docker Swarm and Hipache? Is Hipache discontinued? Is Swarm built on it? Is it compatible?

Also, is it possible to make Swarm answer to the same client IP with the same backend server during a 'session'? This is very important for database applications where the sync after each write may take some time and you don't want the UI to show different states from different servers until the system has settled. Hipache AFAIK doesn't offer this, IMO the biggest downside of this.

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#12

What's the relation between Docker Swarm and Hipache? Is Hipache discontinued? Is Swarm built on it? Is it compatible? Also, is it possible to make Swarm answer to the same client IP with the same backend server during a 'session'? This is very important for database applications where the sync after each write may take some time and you don't want the UI to show different states from different servers until the syst…

Hipache is a reverse proxy, swarm is for managing/scheduling a cluster of docker engines.

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#14
post #8

I've been watching these 5 RCs for a while now because of great additions: - Build time variables: https://docs.docker.com/engine/reference/builder/#arg - docker volume subcommand, finally we have a sane way to clean up left over volumes which are left by default.

That volume subcommand is critical to any description of Docker as "production ready". Docker defaults to leaving volumes "dangling" on the filesystem and there was previously no supported way to remove them. Really glad to see this make it in.

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#15
I am really trying to figure out the ecosystem. I did some stuff with a single server but now as we need to move it to multiple servers we have Rancher, Weave, and so many others (kubernetes?). And now docker has integrated multihost networking so I am really not sure how to proceed.

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#18
post #16

What is the difference between Compose, Swarm, Tutum and Kubernetes? To me looks like you can use each of them to compose a set of containers to run an app.

There was an article posted on HN not too long ago about this.

https://news.ycombinator.com/item?id=10438273

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#19
post #16

What is the difference between Compose, Swarm, Tutum and Kubernetes? To me looks like you can use each of them to compose a set of containers to run an app.

Swarm is a service that sits between your docker cli and your docker engines. It makes it as if you are talking to one docker engine from the cli when in fact you are talking to many. This makes it easier to manage docker engines across multiple hosts.

Compose is a tool that issues commands to docker engines and will e.g. spin up containers and link them together in the right order. It makes rote docker commands a little less painful. It can talk to a single engine or, apparently, many engines via Swarm.

When it comes to putting providing a production "service" based on containers you need to be able to add and remove docker engines, to, for example, deploy new code via rolling update. Google Container Engine (GKE) and Amazon ECS marry docker concepts with front-to-back implementations of hosted infrastructure like server instances and network load balancers. Over-simplified, each has an agent that runs on a docker engine and does work similar to Compose and Swarm against AWS and GCE. Google's daemon is called Kubernetes.

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#20
post #15

I am really trying to figure out the ecosystem. I did some stuff with a single server but now as we need to move it to multiple servers we have Rancher, Weave, and so many others (kubernetes?). And now docker has integrated multihost networking so I am really not sure how to proceed.

I'm biased: use a full PaaS. I like Cloud Foundry because I've worked on it. OpenShift is another alternative.
Post reply on HN