Yeah, well that was the world in 2016. Since than some things have changed in regards of containers - and (traditional) process level isolation is today starting to feel somewhat legacy ;) At least from the security perspective.
@@ThoriumHeavyIndustries do you mean for example we need VPCs to increase security between container processes? Would love to hear your thoughts about this as I'm not very familiar =]
@@7heLostAndDamned There are several projects going on for some time to add a lightweight virtualization layer to container runtimes. The most important project in that direction is KATA, but there are some others. This year we have already seen 3 critical vulnerabilities affecting especially container platforms, so this is surely they way to go if you dont want to intensively dive into SELinux and Seccomp. Baidu did an awseome whitepaper on their use of Kata back in oct.2019. RedHat also has this on their Roadmap for OpenShift probably coming this year.
1. The level at which virtualization happens - virtualization happens at hardware level vs. OS level 2. The type of isolation achieved - isolation of machines vs. isolation of processes 3. How resources are accessed - via hypervisor vs. via kernel features such as namespace and cgroups 4. Flexibility of hardware vs. portability
summarizes the video, but if you would explain it like that in short sentences to someone who never used VMs or containers they would be dumbfounded. like the video and how it introduces you to the main points.
Real sweet-spot delivery: technical content explained clearly and accurately, in accessible and conversational language. My employer holds twice-yearly conventions; I'd give a lot to have Nigel Brown invited as a guest presenter.
💡AHA! Moment here @7:21! We can run VMs and Containers as technologies that can work together not as competing technologies. Great video! Shoutouts to the whole team behind this video! Nigel, you're amazing!
2:17 OS level virtualization --Containers vs hardware level virtualization --VM 4:17 isolation of process --Containers vs isolation of the machine --VM 4:22 different in access: 5:37 different in flexibility(VM) and portability (Container) : [6:03 Docker file] 6:55 Type1 HYPERVISOR & Type2 HYPERVISOR; 7:22 collaboration of type2 HV (flexibility) and Containers(portability) --KubeVirt, new version of Kubernetes, OpenShift.
Great explanation, information and video. I am a former IBMer, I worked for IBM Global Services 1996-1998 supporting LSI Logic's Microsoft's NT 3.52 servers, and Microsoft's NT 4 servers and Lotus Notes servers at IBM's Storage Division in San Jose, California.
I'm really impressed with the explanation as well as the lightboard which has been used. Most tutors use traditional whiteboards or PowerPoint presentations. Technically and content wise this lecture is a class above. Thanks a lot Nigel!!!
Thanks. I’ve been trying to understand containers for an AWS cert exam and other videos were either too detailed or full of vague company jargon that the average person doesn’t understand. This is short, clear, and to the point. Thanks!
Great video. I like the fact that at the end, when the thumbnails for other RUclips videos show up, the main video is turned off and the main screen goes black, but the main video's audio is still audible.
Good video, one addition as this has confused some people I have met. In the VM world we also talk about the host OS. The host OS is the one the HV is running on. In the VMs on top of the HV you have the guest OSes. The difference is that each virtual instance has its own guest OS while the containers run in one OS. This is if you do not use a bare metal HV of course. (Type 1 and Type 2 were a little bit quickly brushed over towards the end) I do like the "isolation of a machine vs. isolation of a process" explanation.
The focus of this video was on Type 1 HV, which is what you're primarily interested in in the scope of cloud applications 2:27. Type 2 was mentioned as an example familiar to many people on consumer level. I agree that VMs hierarchy depiction is misleading. I would draw it like: OS1, OS2, OS3... M1, M2, M3... HV HW
@Jim Allen I work in automotive industry, and don't have much experience using containers. And as I understand the topic of this video, the question is what options does a cloud provider have to organize simultaneous access to the HW resources. The method used must be transparent to you as a customer in any scenario, the differences are only in overhead and security. If you as a customer want to use a container or a HV inside your (likely) VM, you could do it as well (given that nested virtualization is supported). But I think this video doesn't cover such a use case.
Glad you found it useful! Thanks for watching! ✌️ Be sure to check back on our channel from time to time (or even subscribe). We've got more interesting videos coming up.
Nice presentation. You made it so easy to understand. Agree on comments below that the key take away: "VM is isolation of machines, while Containers is isolation of processes". Much appreciate your effort.
By far, this video brought more clarity about containers than the many videosI watched previously. Newbie to cloud engineering and getting my knowledge up for the AZ900 so trying to dissect everything cloud. Thanks for making this much easier to understand and build on!
Thanks Nigel. I am just prepping for my AWS Solutions Architects exam and this explanation was clear, concise and delivered in an enjoyable and engaging style.
Bloody hell man, that was brilliant. This type of video really puts IBM on the map for me. Very informative in a very easy to understand format. This was a precursor for me to understanding Kubernetes for a work project. That's a totally different beast. But for now, I learnt what was essential. Many thanks.
Thank you Nigel for an amazing presentation. The information you presented was so clear and concise despite the gravity of the content. If I can't explain Containers vs VMs to my grandparents, then I don't understand the technology myself. Thank you for allowing me to express my new found knowledge with others.
Well this is the most clear I've been on the difference, but I'm still gonna need like another 5 hours of these discussions before it actually clicks for me from the type 2 perspective.
Very good presentation. I am a type I virtualization guy. I have been looking to get into containers to build my skills. Solid down to earth explanation.
I made an assumption about Type-2 VMs in that Hyper-V, on Windows 10 or Server, was considered Type-2. But according to Microsoft it is actually Type-1. Until I saw this video I was not aware of the Type-1 / Type-2 distinction, even though I was aware that there was or should be one. I enjoyed your video Nigel. Thank you.
Awesome explanation. Thank you, Nigel! One thing is I just couldn't ignore the sharp scratching noise caused by the marking pen which can really drive my brain crazy.
Its so to the point meaning in so simple way , salute to the kind of ur investment to explain so deep in clear crystal policy, where as in internet even videos are unable to a clear picture on it.
By Li Sun 2:17 OS level virtualization --Containers vs hardware level virtualization --VM 4:17 isolation of process --Containers vs isolation of the machine --VM 4:22 different in access: 5:37 different in flexibility(VM) and portability (Container) : [6:03 Docker file] 6:55 Type1 HYPERVISOR & Type2 HYPERVISOR; 7:22 collaboration of type2 HV (flexibility) and Containers(portability) --KubeVirt, new version of Kubernetes, OpenShift.
@@user-xw4mu6nz4t so obvious , is to make it way easier for viewers to check the most important part for them by going to the info they want to get + it's for me as well
I recently started to learn some very basic stuff with Linux about a month ago and my friend was showing me things about containers and docker files (we were using discord). This video was a tremendous help to me now, a month later, in making all that information he was showing me click. Now it makes so much more sense with your simple visual breakdown between VM and Containers. Amazing job!
The conceptual distinction between the two (virtual machines and containers) is just a matter of what level of abstraction your virtualization is occurring at. The former, at the hardware level, and the latter, at the OS level. There is little distinction at all conceptually speaking; they are both forms of virtualization. The overwhelming adoption of Docker speaks to the power of having portability with predictable environments rather than flexibility but not so predictable environments. Docker also does not seem to sacrifice much flexibility either as controlling things like RAM and CPU usage are entirely in Docker’s hands. The two layers of abstraction could indeed work together, but Docker has the upper hand in that it is minimalist, predictable, and then progressively flexible the more specific you are in your configuration.
After trawling RUclips and constantly close videos after the first five seconds due to the guy either - Speaking too fast - Too techy - Is too annoying This video was superb. Great explanation of the different concepts (VM's, Containers, Dockers, etc.). Well done NIgel!
The Docker file builds a Container Image not a container. Also, you totally forgot about SElinux that plays huge role in file system and process isolation in containerisation platform.
Wow, amazed at this man's ability to write backwards! :) (edit: I'm not the sarcastic wit I thought I was. I know it's flipped, as someone pointed out below.) Sincere me: Great and helpful explanation.
VLAN - Virtualization of Switch. (One physical switch pretends to be many switches) VM - Virtualization of Computer (One physical computer pretends to be many computers) Container - Virtualization of Operating System. (One instance of Operating system pretends to be many operating systems) You’re welcome.
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
key sentence is: "VM is isolation of machines, while Containers is isolation of processes"
thats actually pretty deep😂😂
Yeah, well that was the world in 2016. Since than some things have changed in regards of containers - and (traditional) process level isolation is today starting to feel somewhat legacy ;) At least from the security perspective.
@@ThoriumHeavyIndustries do you mean for example we need VPCs to increase security between container processes? Would love to hear your thoughts about this as I'm not very familiar =]
@@ThoriumHeavyIndustries Hi Thorium, can you please share something on what you said?
@@7heLostAndDamned There are several projects going on for some time to add a lightweight virtualization layer to container runtimes. The most important project in that direction is KATA, but there are some others. This year we have already seen 3 critical vulnerabilities affecting especially container platforms, so this is surely they way to go if you dont want to intensively dive into SELinux and Seccomp. Baidu did an awseome whitepaper on their use of Kata back in oct.2019. RedHat also has this on their Roadmap for OpenShift probably coming this year.
1. The level at which virtualization happens - virtualization happens at hardware level vs. OS level
2. The type of isolation achieved - isolation of machines vs. isolation of processes
3. How resources are accessed - via hypervisor vs. via kernel features such as namespace and cgroups
4. Flexibility of hardware vs. portability
Great note taking skills! Bravo & thanks!
That pretty much summarizes the video. Thank you
summarizes the video, but if you would explain it like that in short sentences to someone who never used VMs or containers they would be dumbfounded. like the video and how it introduces you to the main points.
@@PsychoPod the video was pretty simple dude just playy it back it back like i did lol
@@OWUchii I was commenting on the comment, not on the video. Video did a good job explaining everything.
Real sweet-spot delivery: technical content explained clearly and accurately, in accessible and conversational language. My employer holds twice-yearly conventions; I'd give a lot to have Nigel Brown invited as a guest presenter.
Finally someone who can make the topic understandable. Nigel, you and the team that produced this video are great. IBM is really lucky to find you!
💡AHA! Moment here @7:21! We can run VMs and Containers as technologies that can work together not as competing technologies. Great video! Shoutouts to the whole team behind this video! Nigel, you're amazing!
2:17 OS level virtualization --Containers vs hardware level virtualization --VM
4:17 isolation of process --Containers vs isolation of the machine --VM
4:22 different in access:
5:37 different in flexibility(VM) and portability (Container) : [6:03 Docker file]
6:55 Type1 HYPERVISOR & Type2 HYPERVISOR;
7:22 collaboration of type2 HV (flexibility) and Containers(portability) --KubeVirt, new version of Kubernetes, OpenShift.
Great explanation, information and video. I am a former IBMer, I worked for IBM Global Services 1996-1998 supporting LSI Logic's Microsoft's NT 3.52 servers, and Microsoft's NT 4 servers and Lotus Notes servers at IBM's Storage Division in San Jose, California.
Can we get Nigel to do more explanation videos? Super great explanation and very personable speaker!
His my fav.
Couldn't agree more.
Agreed thats the best explanation ive ever heard.
Dude, I wish I had more teachers like you when I was entering the tech field. You have explained this very well in such a short video.
Finally, someone who knows how to demystify vague IT concepts; thanks brother for an absolutely lucid explanation.
I'm really impressed with the explanation as well as the lightboard which has been used. Most tutors use traditional whiteboards or PowerPoint presentations. Technically and content wise this lecture is a class above. Thanks a lot Nigel!!!
I mean its IBM
Dude, I want to hug you - that was a great explanation.
I am a AA female and I loved seeing you on this video tonight! Gave me so much inspiration thanks!!
The best video in the internet explaining this concept. Period
This is best simplest explanation I have seen. Thank you NIgel. I'll look for other videos by you.
Thanks. I’ve been trying to understand containers for an AWS cert exam and other videos were either too detailed or full of vague company jargon that the average person doesn’t understand. This is short, clear, and to the point. Thanks!
Finally I found a clear and clean explanation about these two confusing (at least for me) concepts.
Thank you for excellent presentation!
This guy is great! I really feel like I learned something here, keep it up Nigel!
Hope to see more from this guy, succinctly explained so even novices can understand!
Vraj Patel I completely agree. I’m a pretty not smart person and Mr. Brown here made me feel like I could do anything.
I almost thought you were gonna say the n word O_o
Couldn't agree more! He explains things in way that makes you want to learn more! Thank You so much Mr. Brown.
@@Beerferatu i also agree with you. He is very natural and brings no over-hype voice to his presentation. Just easy to listen to.
Nigel's energy is infectious! Please more videos with him😊
This is super tastefully edited. Compliments to the editor/graphic designers (:
Very well explained Nigel, really liked the way and the speed at which you explained - not too fast or too slow. Keep it up, make more videos. Cheers!
Great explanation. Love the part about "...isolation of process." Makes Docker crystal clear.
Man, that was one of the greatest explanations I've ever seen! Congratulations Nigel and IBM!
Thank you, Leonardo! 🙏 Glad you found it useful!
Finally I understand after hours and hours of reading information. Thanks Nigel!
Great video. I like the fact that at the end, when the thumbnails for other RUclips videos show up, the main video is turned off and the main screen goes black, but the main video's audio is still audible.
Good video, one addition as this has confused some people I have met. In the VM world we also talk about the host OS. The host OS is the one the HV is running on. In the VMs on top of the HV you have the guest OSes. The difference is that each virtual instance has its own guest OS while the containers run in one OS. This is if you do not use a bare metal HV of course. (Type 1 and Type 2 were a little bit quickly brushed over towards the end)
I do like the "isolation of a machine vs. isolation of a process" explanation.
The focus of this video was on Type 1 HV, which is what you're primarily interested in in the scope of cloud applications 2:27.
Type 2 was mentioned as an example familiar to many people on consumer level.
I agree that VMs hierarchy depiction is misleading.
I would draw it like:
OS1, OS2, OS3...
M1, M2, M3...
HV
HW
@Jim Allen I work in automotive industry, and don't have much experience using containers. And as I understand the topic of this video, the question is what options does a cloud provider have to organize simultaneous access to the HW resources. The method used must be transparent to you as a customer in any scenario, the differences are only in overhead and security.
If you as a customer want to use a container or a HV inside your (likely) VM, you could do it as well (given that nested virtualization is supported). But I think this video doesn't cover such a use case.
I so loved this. Im working with VMs and interested in moving to containers so this helps a lot
Glad you found it useful! Thanks for watching! ✌️
Be sure to check back on our channel from time to time (or even subscribe). We've got more interesting videos coming up.
Nice presentation. You made it so easy to understand. Agree on comments below that the key take away: "VM is isolation of machines, while Containers is isolation of processes". Much appreciate your effort.
This is the best explanation of this I've ever seen
By far, this video brought more clarity about containers than the many videosI watched previously. Newbie to cloud engineering and getting my knowledge up for the AZ900 so trying to dissect everything cloud. Thanks for making this much easier to understand and build on!
Thanks Nigel. I am just prepping for my AWS Solutions Architects exam and this explanation was clear, concise and delivered in an enjoyable and engaging style.
Great video. I’ve been passively wondering what’s the difference for months. U gave me the answer spot on
Thanks for watching, Emil! 😃
Nigel's killing it. Sure-footed and warm.
Thank you! That’s the exact difference I needed to hear. VM is at the OS level and containers are at the process level.
Dudes enthusiasm makes it easy to understand. Loved it! Love me some containers!
Nigel!!!! This is exactly how I remember you in Production School! lol. Great Teacher, Great Mind, Great Person! Tell mom I said Hi!
The easiest and best explanation that I have seen on youtube about containers vs VM! Nicely done!
Nigel killed this. Get this guy in more videos!
This is my third video on containers, and I finally get it. Excellent explanation!
Damn this was thoroughly explained and simplified
Bloody hell man, that was brilliant. This type of video really puts IBM on the map for me. Very informative in a very easy to understand format. This was a precursor for me to understanding Kubernetes for a work project. That's a totally different beast. But for now, I learnt what was essential. Many thanks.
You're welcome, Steve, and thanks for the great feedback! 🙏 Be sure to subscribe for more videos like this one. 😉
Thank you Nigel for an amazing presentation. The information you presented was so clear and concise despite the gravity of the content. If I can't explain Containers vs VMs to my grandparents, then I don't understand the technology myself. Thank you for allowing me to express my new found knowledge with others.
It's 2AM and i'm watching tech videos for no reason, they just make me feel good idk why
🙌🔥
Well this is the most clear I've been on the difference, but I'm still gonna need like another 5 hours of these discussions before it actually clicks for me from the type 2 perspective.
this bro is just amazing. I took notes of every word he said and understood every bit of it. Thank you bro.
Finally someone managed to explain this in a way that even I could grasp.
Excellent overview -- agree with Rick Chow on the isolation difference - thanks
Very good presentation. I am a type I virtualization guy. I have been looking to get into containers to build my skills. Solid down to earth explanation.
Thanks for watching, Dewayne! 💙
Great video and explanation. I have went through training but this is one of the best explanations that I have had. Thanks for sharing.
This helped me with my Security plus cert, thank you!
I made an assumption about Type-2 VMs in that Hyper-V, on Windows 10 or Server, was considered Type-2. But according to Microsoft it is actually Type-1. Until I saw this video I was not aware of the Type-1 / Type-2 distinction, even though I was aware that there was or should be one. I enjoyed your video Nigel. Thank you.
Awesome explanation. Thank you, Nigel! One thing is I just couldn't ignore the sharp scratching noise caused by the marking pen which can really drive my brain crazy.
I'm 100% with that, the scratching noise is really troubling- wonder why it was not there in some other videos.
Level of isolation:
VM: isolation of machines (hardware resources: CPU, RAM, and Network)
Container: isolation of processes
Dude you know your stuff so easy to listen to--you are probably great to alongside with!!!
Nice job Nigel, making us IBMers proud!
One comment -- none of this is specific to Linux, all of it can run on Windows, System z, etc, etc.
Wow! It was explained in a very simple way. I think I can show it to my grandma and she will get this
Can we get a video explaining how the presenter was able to write in reverse writing so well?
It's something called light board (ruclips.net/video/wCOuu0-o5YI/видео.html).
The footage you're seeing is already flipped.
Hint: mirror image.
That's correct! 👍 Here is a blog post we wrote that explains how we do it. ➞ ibm.co/3eItmz7
they probably flipped/mirrored the video
hint: he's not left-handed
Its so to the point meaning in so simple way , salute to the kind of ur investment to explain so deep in clear crystal policy, where as in internet even videos are unable to a clear picture on it.
This was the first explanation of containers that I actually understood!
Great explanation! And thank you for the education and representation 🙏🏾✊🏾
Clear, concise, digestible lesson. Very impressed
By Li Sun
2:17 OS level virtualization --Containers vs hardware level virtualization --VM
4:17 isolation of process --Containers vs isolation of the machine --VM
4:22 different in access:
5:37 different in flexibility(VM) and portability (Container) : [6:03 Docker file]
6:55 Type1 HYPERVISOR & Type2 HYPERVISOR;
7:22 collaboration of type2 HV (flexibility) and Containers(portability) --KubeVirt, new version of Kubernetes, OpenShift.
What was the point of this comment?
@@user-xw4mu6nz4t so obvious , is to make it way easier for viewers to check the most important part for them by going to the info they want to get + it's for me as well
Awesome job explaining these topics! Please have Nigel in more videos!!!
Great video. You did an awesome job explaining the strength of both VMs and containers.👍🏽
I recently started to learn some very basic stuff with Linux about a month ago and my friend was showing me things about containers and docker files (we were using discord). This video was a tremendous help to me now, a month later, in making all that information he was showing me click. Now it makes so much more sense with your simple visual breakdown between VM and Containers. Amazing job!
Thank you!
The conceptual distinction between the two (virtual machines and containers) is just a matter of what level of abstraction your virtualization is occurring at. The former, at the hardware level, and the latter, at the OS level. There is little distinction at all conceptually speaking; they are both forms of virtualization. The overwhelming adoption of Docker speaks to the power of having portability with predictable environments rather than flexibility but not so predictable environments. Docker also does not seem to sacrifice much flexibility either as controlling things like RAM and CPU usage are entirely in Docker’s hands. The two layers of abstraction could indeed work together, but Docker has the upper hand in that it is minimalist, predictable, and then progressively flexible the more specific you are in your configuration.
thank you for differentiating between vm and container in a clear manner
That was actually very well explained. So clear.
Excellent concise explanation, thanks Nigel!
Thank you , this helped me understand difference between VMs and Containers
We're so happy to hear this! 🙏 Be sure to also check out the links in the video's description for more resources. ⤴️
After trawling RUclips and constantly close videos after the first five seconds due to the guy either
- Speaking too fast
- Too techy
- Is too annoying
This video was superb. Great explanation of the different concepts (VM's, Containers, Dockers, etc.). Well done NIgel!
Wow! What an awesome video! Thanks, Nigel!
Beautifully and effectively presented!
Great Explanation - you made it so easy for me to understand containers as compare to VM .
Perfect, hats off to Nigel
Great job explaining this in human. Thanks Nigel.
Clear and concise explanation
Such a great explaination. By illustrating how VMs vs Containers are built, you clarifed alot. Thank you good sir!
Nigel, you explained PERFECT! Loved this presentation!
Most excellent presenter and presentation!
Best explanation I found ! Thanks
At last, what I've tried to tell folks! You nailed it!!! Containers aren't virtual machines ;)
Ikr! So many people kept saying they are both VMS. But he made it clear that both achieve VIRTUALIZATION but in different ways
Great job Nigel..!! Glad you did this post...
Folks and IBM Cloud, any other videos by Nigel? I've been searching.... This was brilliant!
Nice video and explanation was nice , anyone new to these terms also understands this.
Very well structured, Nigel
Great explanation Nigel, the concepts stuck in my head.
Subscribed.
Nigel, it would appear, has found a really good niche and format IBM.
Chase after it!
Awesome video. Awesome speaker. Clear and concise and easy to follow
wow I wish I had a teacher like you in my bachelors.
This was a WONDERFUL explanation! Thank you!
EXCELLENT explanation and presentation!
Simple and easy to understand. Well done. Thank you
cant get my mind off the fact that he is writing in reverse with so much ease
The Docker file builds a Container Image not a container. Also, you totally forgot about SElinux that plays huge role in file system and process isolation in containerisation platform.
Respect to Nigel! Very cool explanation!
Wow, amazed at this man's ability to write backwards! :)
(edit: I'm not the sarcastic wit I thought I was. I know it's flipped, as someone pointed out below.)
Sincere me: Great and helpful explanation.
Great explanation - very clear to me as a layperson.
Happy to hear that, Rafael! 🙏
VLAN - Virtualization of Switch. (One physical switch pretends to be many switches)
VM - Virtualization of Computer (One physical computer pretends to be many computers)
Container - Virtualization of Operating System. (One instance of Operating system pretends to be many operating systems)
You’re welcome.
Crystal clear presentation of conceptual application approach anchoring the basis of difference between elements and beyond environment.