News for hackers. Stuff that matters.
Re:Docker 1.2.0, with restart policies by cpuguy83 on Friday August 22, 2014 @02:54PM (#8213430)
The cgroups and namespaces do indeed provide a layer of security. We also drop certain capabilties, so for instance root inside the container can't (by default) manipulate iptables, mount things, change network settings, etc. To come later would also be user namespaces so root inside the container != root outside the container. There's also a significant amount of support within Docker for selinux/apparmor stuff.

Indeed, all these things come together to do exactly what jails does.

Jails do not provide the same security as a VM, just like what Docker does is not providing that same level of security. You are kidding yourself if you think jails does.

It's all layers... like ogres... or onions :)

Re:Docker 1.2.0, with restart policies by Alupis on Friday August 22, 2014 @03:52PM (#8213646)
I get the PR angle... But over-representing Docker is doing more harm than good. People are reading things like "We would like to add feature X" or "Implementing feature X is on the roadmap", but interpreting it as "Docker does all these things right now". Soon people will be talking about how Docker makes pizza too.

Can Docker be secure? Sure -- is it? No.

Re:Docker 1.2.0, with restart policies by cpuguy83 on Friday August 22, 2014 @04:17PM (#8213743)
These are all things that are there now, except user namespaces (which is indeed huge), not roadmap items.