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

Google Launches Managed Service for Running Docker Apps on Its Platform

googlecloudplatform.blogspot.com

Post reply on HN
Print view View original

61–69 of 69 posts

Re: Google Launches Managed Service for Running Docker Apps on Its Platform

#61

Post by ossreality »

23david wrote: post #48
jbeda wrote: post #43

Earlier quoted context omitted.

Stable production ready GKE will gate on Kubernetes. Our Kubernetes roadmap is here: https://github.com/GoogleCloudPlatform/kubernetes/blob/maste... We are driving aggressively here. I hate to put a date on it but things are converging.

Ok that's fair, but just a rough idea would be incredibly helpful. Are we talking sometime within the next 6 months / 12 months / longer? That roadmap document doesn't really explain how the current featureset makes Kubernetes ready for an 'alpha' release on GKE.

100% yes.

Re: Google Launches Managed Service for Running Docker Apps on Its Platform

#62

Post by nl »

jff wrote: post #56
abakker wrote: post #53

Earlier quoted context omitted.

As someone who doesn't know, why would you want to run VMs inside of a docker container? Wouldn't this have tremendous overhead relative to just running the hypervisor?

If you use the -privileged flag, docker containers can access /dev/kvm and start low-overhead KVM instances. It's advantageous for me, because I can say "hey check out this software" and they just have to run a single docker command, compared to installing Go, apt-getting a bunch of packages, fetching our repo, compiling, etc.

Why do you need the VM (as opposed to just containers)?

Re: Google Launches Managed Service for Running Docker Apps on Its Platform

#63

Post by superuser2 »

jbeda wrote: post #12
wstrange wrote: post #10

Earlier quoted context omitted.

My biggest question on Docker / k8s: How does one control where persistent data lives and the required performance characteristics? Example: I need SSD + a certain level of availability? Is there a good strategy for managing this?

Right now, it isn't plumbed in but it is on the roadmap. Either (a) you have network based block device and the master/manager maps that to a machine dynamically as the container get scheduled or (b) you constrain the containers to machines that have the hardware/data you need. (b) is less than ideal but sometimes necessary. Some discussion: https://github.com/GoogleCloudPlatform/kubernetes/issues/598

This is THE open question for Docker right now. The first person to actually solve it is going to be in a pretty damn good place.

Docker could make most infrastructure-level "cloud" abstraction obsolete and let people run resilient, scalable clusters on hardware pretty easily. There's CoreOS, Kubernetes, and a few others in the app-instance-scheduling space, but right now, if you want persistent data storage of any kind (block, SQL, blob, whatever) then you still need to tie things down to an individual machine or use VM-level cloud technology to acheive some semblance of fault tolerance. The inability to do persistent storage in a reasonable way is, from where I sit, the main thing keeping Docker from eating the world.

When you can run Postgres in a stable/supported way in a container on my own hardware that gets scheduled around failure/crowding/etc, you no longer needs AWS, VMWare, etc. That could be huge.

Re: Google Launches Managed Service for Running Docker Apps on Its Platform

#64

Post by jchonphoenix »

RenegadeofFunk wrote: post #58
krschultz wrote: post #52

Docker has pulled off some really impressive biz dev. I can't think of too many other things that Azure, Google Cloud, and AWS all support.

Strongly agree with this. I've been interviewing for DevOps jobs and it seems like everyone thinks they need to be using Docker for some reason or another. Studying up on it has improved my interview feedback substantially.

If you're interested, I run a team at Docker and would love to chat :P

Re: Google Launches Managed Service for Running Docker Apps on Its Platform

#65

Post by wastedhours »

superuser2 wrote: post #63
jbeda wrote: post #12

Earlier quoted context omitted.

Right now, it isn't plumbed in but it is on the roadmap. Either (a) you have network based block device and the master/manager maps that to a machine dynamically as the container get scheduled or (b) you constrain the containers to machines that have the hardware/data you need. (b) is less than ideal but sometimes necessary. Some discussion: https://github.com/GoogleCloudPlatform/kubernetes/issues/598

This is THE open question for Docker right now. The first person to actually solve it is going to be in a pretty damn good place. Docker could make most infrastructure-level "cloud" abstraction obsolete and let people run resilient, scalable clusters on hardware pretty easily. There's CoreOS, Kubernetes, and a few others in the app-instance-scheduling space, but right now, if you want persistent data storage of any k…

This is also what's holding me back from delving into Docker more. Love the concept, and the workflow, but trying to get my head around how the persistent data storage will work is still troubling me.

Re: Google Launches Managed Service for Running Docker Apps on Its Platform

#67

Post by tianon »

shykes wrote: post #59
philip1209 wrote: post #8

Earlier quoted context omitted.

Some google-managed base images would be helpful. The last time I checked, some of the major public docker images were still shellshock-vulnerable. Pre-installed GCE tools would be helpful. Perhaps automated environment variables about region, etc.

If you have found an official Docker image that is still shellshock vulnerable, the library maintainers [1] would love to hear from you as they take that stuff quite seriously. As far as I know the entire library is fully patched. [1] https://github.com/docker-library/official-images

As one of the maintainers in question, I'd absolutely mirror this whole statement: if any of the image upstreams have an important update available that isn't applied, we're very interested in rectifying that.

Re: Google Launches Managed Service for Running Docker Apps on Its Platform

#68

Post by dln_eintr »

vertex-four wrote: post #41
bjt wrote: post #35

Earlier quoted context omitted.

I'll give it a shot, with the disclaimer that this explanation is based on conference talks I've seen and documentation I've read. Spark is a successor to Hadoop, aiming to perform big distributed data crunching jobs more quickly by not limiting itself to a map-reduce paradigm and by holding more data in memory. Apache Mesos is a resource scheduler for a cluster of machines. It is architected to be agnostic about the…

> and not used so much for long-running services like a web app Mesosphere Marathon, which sits on top of Mesos, makes doing long-running services easier; it starts services, restarts them if machines crash, etc etc. Where Mesos is the resource schedular, Marathon is more like a *nix init system. Aurora is supposed to do much the same thing, but is in Incubation at the moment. There's also "Singularity", which does a…

Kubernetes also fits very well with Mesos for scheduling.

Check out https://github.com/mesosphere/kubernetes-mesos

Re: Google Launches Managed Service for Running Docker Apps on Its Platform

#69

Post by jff »

nl wrote: post #62
jff wrote: post #56

Earlier quoted context omitted.

If you use the -privileged flag, docker containers can access /dev/kvm and start low-overhead KVM instances. It's advantageous for me, because I can say "hey check out this software" and they just have to run a single docker command, compared to installing Go, apt-getting a bunch of packages, fetching our repo, compiling, etc.

Why do you need the VM (as opposed to just containers)?

Because the software I'm attempting to demonstrate/distribute is specifically designed for running VMs. That is its sole purpose--sorta like OpenStack.
Post reply on HN