Re:Don't expose the docker socket, even to a container
by acconsta on Thursday September 24, 2015 @01:35AM
(#10270010)
No, but the Gmail team might be worried about some Russian guy finding a buffer overflow in YouTube's application. Then what? They can escalate privileges and read your email?
[ Parent
| on HN ]
Re:Don't expose the docker socket, even to a container
by KirinDave on Thursday September 24, 2015 @02:32AM
(#10270170)
Google's deployment of Docker is less susceptible to this. They do additional partitioning of applications.
Re:Don't expose the docker socket, even to a container
by acconsta on Thursday September 24, 2015 @03:11AM
(#10270295)
Yeah... so it seems like Linux containers can be sufficiently hardened?
Re:Don't expose the docker socket, even to a container
by the_mitsuhiko on Thursday September 24, 2015 @06:40AM
(#10270863)
Not really. You physically seperate gmail and youtube.
Re:Don't expose the docker socket, even to a container
by acconsta on Thursday September 24, 2015 @01:36PM
(#10273129)
Source? How do you get 80% CPU utilization if you have to physically separate all your job types?
http://csl.stanford.edu/~christos/publications/2015.heracles...
Re:Don't expose the docker socket, even to a container
by geofft on Thursday September 24, 2015 @06:10PM
(#10275104)
Google has way more applications than just Gmail and YouTube.
Basically, if someone breaks into Gmail, you're already in deep trouble. You're not significantly better off because they didn't break into Hangouts. Same in the other direction. So you can run those on the same hardware.
If you think YouTube is less sensitive than Gmail (I don't know if Google actually does), you can separate those, sure. But there are enough applications that are no worse to break into than YouTube, like Photos. You can run those on the same hardware.
At Google's scale it's not too hard to say, this is the stuff we're ridiculously paranoid about and this is everything else, and get 80% CPU utilization on both infrastructures.