Docker 1.12: Now with Built-In Orchestration

I chose Docker for my project with hope that it would help me create an easily reproducible development environment... And I'm not really sure if it was a good idea. There's so many moving parts and I can't name one that actually works well. Configuring storage is a hell (running out of disk space can lead to errors that are really difficult to debug), the dance with bridges makes configuring firewall a terrible experience. I definitely wouldn't recommend it as a stable container solution.

Just based on the details mentioned in the keynote, the services API and swarm features look very similar to what&#x27;s offered by Kubernetes... service discovery, rolling updates, load balancing, health checks, auto-healing, advanced scheduling.<p>I guess this was to be expected, but it&#x27;s also kind of sad. I think it would have been a more strategic move to embrace Kubernetes instead of trying to compete with it.

I wish they would address stability issues first, like this bug[1] that has been around 2 years and is still happening on the latest versions.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;issues&#x2F;5618" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;issues&#x2F;5618</a>

This seems like a really exciting, albeit natural, evolution of the Docker &quot;platform&quot;. It&#x27;s really true that no one cares about containers, everyone just wants their apps to work.<p>That being said the one giant omission from Docker is still seems to be management of volumes&#x2F;data. Great, we can run 100 nodes on AWS in a matter of minutes, but if your system has data storage requirements (ex: Almost every database ever) ... You&#x27;re kinda left up to your own still. How does Docker Orchestration migrate the data volumes?<p>They really tried to sell this as &quot;You don&#x27;t need to do anything but the AWS beta, the DAB and a few commands&quot; which would be wonderful. However with the need for reliable data storage... you&#x27;re still stuck doing everything &quot;the old fashion way&quot;.<p>(Edit: No, I don&#x27;t mean store data IN the container, I presume no one is that silly. I meant the attached volumes. No volume mgmt = less greatly less helpful).

I&#x27;m not surprised the Kubernetes primitives got copied into this. I had stated before that Kubernetes was what Docker wants to be when it grows up -- and maybe that time is here. Having used Kubernetes in production, I don&#x27;t know robust the Docker orchestration primitives are in comparison. But I&#x27;ll probably find out soon.<p>The big advantage having a built-in Docker orchestration is that Kubernetes is painful to install from scratch. (Yes, there are scripts to help mitigate this; yes, GKE is effectively hosted Kubernetes). I&#x27;m involved in another Dockerization projection, but we don&#x27;t know if we want to invest the time into setting up Kubernetes (though GKE is an option). This would be a good time to check things out.<p>Just to show how quickly things change. In 2015, I tried the docker compose, AWS ECS, and Kubernetes for production deployment, and of all of them, Kubernetes addressed the pain points in a practical way. The Kubernetes project ended in late 2015, and now six months later, things changed again ...

At first I was worried that this is yet another Raft implementation, but it seems they&#x27;re building on etcd&#x27;s version [1] which should be a win for everyone trying to prove correctness for the various implementations.<p>1. <a href="https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;swarmkit&#x2F;blob&#x2F;a78a157ef66adf0978f031e7bbc9bff2c16df9a0&#x2F;manager&#x2F;state&#x2F;raft&#x2F;raft.go#L19" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;swarmkit&#x2F;blob&#x2F;a78a157ef66adf0978f0...</a>

I also noticed that now &#x27;Docker for mac&#x27; is available without beta invite. I just downloaded and installed though its version is 1.12.0-rc2.<p>Maybe they will make formal announcement when 1.12 for mac is released.

I wish docker released lite version of docker. Only containerisation, no networking configurations, weird cache mechanisms - just something small and easy to use locally.<p>No one sane will run docker on prod anyway.

The new orchestration looks based on Swarm and possibly Compose; have they resolved the issue where the lack of lifecycle semantics means that your services don&#x27;t work if they have any sort of cluster semantics, like Riak, Cassandra or Zookeeper? These previously always required outside hacks to work, and work flawlessly with Kubernetes. It looks like there&#x27;s some service discovery support; which may or may not fit the bill.

I find it super amusing that GCE isn&#x27;t mentioned, that ostensibly Kubernetes is the source of lock-in (despite being open-source and likely having more cycles on EC2 than on GCE&#x2F;GKE), and that this proudly uses gRPC for http&#x2F;2 and protobuf goodness. So which is it, is Google an evil vendor trying to lock you in, or are we actually doing work in the open and just hoping you&#x27;ll choose us when you want infrastructure?<p>Disclaimer: I work on Compute Engine, and think of the Kubernetes folks as friends.

If someone else also want to see the keynote, they have a recording: <a href="http:&#x2F;&#x2F;www.ustream.tv&#x2F;recorded&#x2F;88610090" rel="nofollow">http:&#x2F;&#x2F;www.ustream.tv&#x2F;recorded&#x2F;88610090</a>

I have two code bases that are microservices. I thought using Docker would be easy to setup and share a redis instance between these services. After spending a day trying various thing I just gave up and did &#x27;brew install redis&#x27; and got back to real app dev. Docker isn&#x27;t streamlined enough, does have great examples and is still changing lots. Sometimes doing it the old fashioned way is what lets you ship features faster.

Omg their navigation bar covers half my screen! Seriously, why do companies inside upon reducing my screen real estate for stupid shit?

Great, now make it a first class citizen in compose and mix in docker-machine&#x27;s provisioning capabilities!

The article is lots of blah blah plus &quot;lock-in&quot; for good measure, with exactly zero code or configuration examples, and it reads like a snake oil salesman brochure. I&#x27;m still skeptical about the purported advantage of Docker &#x2F; Linux over zones &#x2F; SmartOS.

I was using osx beta but uninstalled it for now because docker was eating all my space without recovering it after deleting containers. Anybody using rkt for dev wants to share their experiences, I am thinking about trying it but would not invest time if it is not ready yet.

Have they sorted out storing secrets yet? That&#x27;s one thing I noticed that Kubernetes manages that docker is still scratching it&#x27;s head over.<p>But this looks like it could be great progress. Orchestration was always the main pain that stopped me from using docker.

This is great. I can&#x27;t wait for an ARM build, though.

Docker is great (wonderful in fact) for building development&#x2F;CI environment. I never use docker for production.

Maybe i&#x27;m not uptodate or misunderstanding, but doesn&#x27;t Mesos&#x2F;Mesosphere do something similar?

is docker as good as rkt nowadays?