Re: Container == process
It's slightly more than that - it's a way to easily share and distribute that chroot directory with associated library dependencies.
It's a way to share config amongst the directories and to obfuscate the networking to the point where an epileptic spider dipped in ink would be considered coherent.
IIRC there is also a bit more memory protection than a plain chroot process has - but I might be wrong about that.
Biting the hand that feeds IT
