News for hackers. Stuff that matters.
Re:High-process-count support added to master by icebraining on Tuesday August 15, 2017 @05:02PM (#15022534)
Docker is just regular processes limited by a bunch of Linux kernel isolation mechanisms, which means that you're subject to potential kernel exploits, which would allow a "neighbor" container to run code outside the container and then control your own.

There are some ways of mitigating this, but the simplest one would be for the provider to run a VM for each container, then you get the security guarantees of regular VMs (though you still have to trust the provider to keep the OS up to date).

Re:High-process-count support added to master by marktangotango on Tuesday August 15, 2017 @05:50PM (#15023003)
Is a docker container simply a process or is it more heavy weight than that? It certainly can be, so isn't this characterization that it's merely a "process" a bit disingenuous?

https://unix.stackexchange.com/questions/216618/what-do-the-...

Re:High-process-count support added to master by icebraining on Tuesday August 15, 2017 @06:20PM (#15023244)
Processes, not process, and I was talking in terms of security, but even in terms of performance, yes, it mostly is. There are some Docker features that can be more expensive (NAT and layered filesystem), but they are optional. A "Docker container" itself is just a group of processes to which the kernel applies a different policy than the default.

I'm not sure what that link is supposed to show, can you be more clear?