> Containers are marketing slang for operating-system virtualization.
Containers are considerably more than virtualization[1], which is why jails/zones/kvm never took off, but Docker did.
> Oh really? So containers are not isolated to each other...that's some news...bad ones
Indeed, containers make for very poor security boundaries. But there are upsides to sharing the same kernel.
> composibility....stop with that stinking shit please.
Are you unfamiliar with "composition" as a software design/architecture term? One can create and bundle (Docker) containers that work together and have a shared network interface in a way that jails can't. As an example, a reverse proxy + service backend + db working in concert.
1. Disk storage format, standardized packaging descriptor, repository.
It's like you don't even understand what a container is, let alone comparing kvm with jails.
Then giving a example that is a piece of cake for jails/zones...even in a concert.
Please educate yourself about zones, brandedzones and lxzones (for the solaris/illumos) or jails (for the bsd side) it's really interesting i can tell you, and additionally you don't sound like marketing blabla after that.
>the lack of isolation is what enables composibility of containers
Oh really? So containers are not isolated to each other...that's some news...bad ones ;)
BTW are you from a marketing department? ....composibility....stop with that stinking shit please.