Chris Green wrote: > I'm trying to get my mind round the various ways of wrapping/isolating > collections of code and programs in Debian (well in any Linux I > suppose) and I'm really not understanding them very well. When you go > to the home of any particular one it seems to think you know what it > is already and thus goes from there to tell you how to install it but > doesn't really explain what it does.
Containers are similar to virtual machines in effect.
Compared to full virtualization, they have much lower
overhead (which can be great) and much less isolation
between the host and container (which can be not so great).
Since they don't run their own kernel, they don't boot, so
starting a container takes a trivial amount of time compared
to starting a virtual machine.
Try either or both of these for more details:
https://ubuntu.com/blog/what-are-linux-containers
https://www.redhat.com/en/topics/containers/whats-a-linux-container
--
Todd
signature.asc
Description: PGP signature
