Docker in Production: An Update

Re:Docker in Production: An Update by crb on Thursday February 23, 2017 @11:52AM (#13715358)

It's great that hftguy thinks Google Container Engine is stable (I work on it) but I'm sorry to say it's very easy to prove that is, in fact, running Docker on the nodes.

You can just SSH into one and see for yourself.

Kubernetes was built from the ground up to orchestrate Docker. CoreOS did a lot of work to make it possible to trade rkt in for Docker's engine, and the cri (Container Runtime Interface) is now generalising that so that there is a clear abstraction between the kubelet and the engines it orchestrates. Read about it here: http://blog.kubernetes.io/2016/12/container-runtime-interfac...

If you want to do things that are different to what we provide support for on GKE as a Managed Service (tm), you're able to run your own Kubernetes clusters on GCE. (We do let you run a Kubernetes alpha version, but only on non-supported clusters that self-destruct after 30 days.

[ Parent | on HN ]

Re:Docker in Production: An Update by Draiken on Thursday February 23, 2017 @01:15PM (#13716218)

We very recently moved from some bare-metal pet machines into Google GKE and couldn't be happier.

Honestly the hardest thing is keeping up with how fast Kubernetes evolves and gets better and better. The same goes for all Google services (pubsub, bigquery, etc)

We started the migration on Kubernetes 1.1 and are now live on 1.5.1

Even using it for things we probably shouldn't (old stateful applications) without a single problem. At least no Docker related problems.

I don't know, this article seems to be very presumptuous. A lot of bold claims, little backing and, as you state, some pretty false claims.

TBH I don't know why it's among the top of HN

[ Parent | on HN ]

Re:Docker in Production: An Update by SEJeff on Thursday February 23, 2017 @01:51PM (#13716587)

Is it eventually going to run rkt/cri-o/lmctfy?

[ Parent | on HN ]

Re:Docker in Production: An Update by crb on Thursday February 23, 2017 @02:42PM (#13717038)

If you're a customer and you're interested in either of the first two, please ping me an e-mail.

GitHub's lmctfy README states "We are not actively developing lmctfy further and have moved our efforts to libcontainer."

[ Parent | on HN ]

Re:Docker in Production: An Update by wmf on Thursday February 23, 2017 @02:29PM (#13716913)

So what magic combination of distro + FS do you use to make Docker stable?

[ Parent | on HN ]

Re:Docker in Production: An Update by crb on Thursday February 23, 2017 @02:40PM (#13717026)

The default distro is Container Optimised OS: https://cloud.google.com/container-optimized-os/docs/. It's derived from Chromium OS, which means we can take advantage of the team who build images for the many devices which use it, and the security response infrastructure around it.

With 'docker info' on a node you can see we use OverlayFS, which seems a popular choice in the community also: http://burkelibbey.s3.amazonaws.com/dockercon-fs.pdf

[ Parent | on HN ]

Re:Docker in Production: An Update by user5994461 on Thursday February 23, 2017 @03:23PM (#13717407)

So, customized Google OS, but using the official Docker package? Oh wait. How could there be an official docker package for an OS noone known existed?

I assume customized kernel as well? and where does the overlay drivers come from? How much custom back-ports and custom development?

The article is not on point to say GKE replaced docker entirely then... but you are not point to deny and pretend that you are running Docker on anything remotely common.

[ Parent | on HN ]

Re:Docker in Production: An Update by crb on Thursday February 23, 2017 @05:13PM (#13718317)

Chromium OS is open source: https://www.chromium.org/chromium-os. OverlayFS is in the upstream Linux kernel.

CoreOS is a very similar idea, and given that, we don't make builds of the container images available outside GCE.

Customers who need specifics of the OS (that they can't find them by just looking at the kernel config on the node) are welcome to ping us a support ticket.

[ Parent | on HN ]