October 2016
Beginner to intermediate
416 pages
11h 11m
English
When Microsoft had people start testing and using containers, what they found is that many places were deploying only one container per VM. Well, that’s a little silly – sure they are getting the DevOps benefits out of using the container approach, but you aren’t getting any benefits out of the resource sharing and small footprint of a container. After doing a little digging, they discovered that companies were doing this because containers natively share kernel. While this is imperative to the performance of containers, this is a problem for isolation, and organizations were reluctant to deploy multiple containers within a single VM. So, Microsoft created a compromise.
When spinning up your containers, ...
Read now
Unlock full access