News for hackers. Stuff that matters.
Re:Don't expose the docker socket, even to a container by jkyle on Wednesday September 23, 2015 @10:58PM (#10269576)
KVM & VMWare are not containerization, they're full virtualization.

There are a lot of benefits to containers and they don't have to be insecure. More efficient resource utilization and orders of magnitude faster allocation and launching to name two.

Google runs a significant portion of its internal operations in a container infrastructure and has for quite a while.[1]

They're perfectly capable of deployment into production environments.

I won't comment on docker as I haven't spent the time to fully grok all its warts.

1. http://research.google.com/pubs/pub43438.html

Re:Don't expose the docker socket, even to a container by _yy on Thursday September 24, 2015 @04:52AM (#10270530)
> Google runs a significant portion of its internal operations in a container infrastructure and has for quite a while.[1]

They use containers inside virtual machines. Virtualization for security, containers for deployment.

Re:Don't expose the docker socket, even to a container by jkyle on Thursday September 24, 2015 @01:02PM (#10272859)
I know from Joe Beda's talk [1] they run vm's inside containers for scenarios where they need a managed os. And that those containers run on bare metal. But I can't speak to the reverse not being an employee or authority on Google's internals.

1. https://speakerdeck.com/jbeda/containers-at-scale