*Modern UKpostsrs jump cutting every misplaced vowel and topic change* >Dave enunciating every word of a technical topic for four minutes straight without ever breaking eye contact

My favorite guy from the MS DOS and Win95 days, explaining something i've been curious about. I have only used virtual machines, but i've supported systems using docker.

now explain what Kubernetes is

Just a note, you technically don't need to learn how to create Dockerfiles, since, just like in a VM, you can create a simple base container (like Debian or Ubuntu or something), open an interactive shell inside the container and configure it however you want like you normally would on a normal system, after which you can run "docker commit" on that container to get an image with all the changes you performed, which you can use similarly how you'd use VM snapshots.

As a older due who got diagnosed with ASD/ADHD at age 59, I often come to your channel for explanations of things that I just can't seem to digest from others. Thanks.

a bare metal server is a house. you have your plot of land and your house. it is all yours. a VMhost is an apartment block. each server is a suite, but share the infrastructure (plumbing, stairs, building door). a container is a bed in an army barracks. you share everything.

Dave, thank you. I’ve held jobs including help desk tech, network admin, systems engineer, and cloud architect since 2013. I’ve asked half a dozen people how containers were different than VMs, and nobody has ever been able to answer the question like you have. Your statement “if you get ring 0 access on the container, you get it for the whole machine” made it click for me.

As someone who has been kicking around the IT industry in a variety of roles for 30 years, I understand all the words coming out of your mouth, but this particular video for some reason gave me an unanticipated appreciation as to why it is in so many far future sci-fi settings, technology is more or less treated like magic. Not because it is hyper-advanced and thus indistinguishable from magic in the Clarke sense, I'm talking settings like Warhammer 40K or Fading Suns or even Battle Tech, where a lot of it is either possible now or will be in our near future, where the in-game civilizations had peaked at something far beyond us today but then collapsed and regressed all the way back, and all the people who understood the technology and how to create and operate it were almost all wiped out, so extremely few people remain who can even keep the existing stuff running, much less invent new stuff. And in some cases, the knowledge of how to maintain the technology has become ritualized into religious like ceremonies. Which is to say, even without an intentional targeting of people who can create and maintain these technologies, how many people today actually truly fully comprehend how this stuff works? Much less can build it from scratch in a clean room? So very few... And yet so much of the world today is critically reliant on this stuff! Kind of nerve-racking when you really think about it.

"Get ready to drink from the firehose of knowledge" What a *vivid* metaphor! 🤓😁🤭

"It works on my machine" - my most hated line from my time in QA and build management. 😂

I love this channel, no frills just quality content throughout

I worked with IBM's VM in the early 70's. Big iron cannot be beat. What wonderful machines they were and still are. Amazing!

It is not like I'm deifying Dave, it's just this phenomena when I already used a lot of hypervisors, troubleshoted many problems with containers, and got my knowledge in shreds and patches. And then I listen to this summary by Dave and everything goes into its designated place in my head forming a solid structure of knowledge. It happens from time to time to us specialists, when the last book that we read on some subject is so crystal clear to us like it was specifically tailored for our brain to understand, when in reality it's just the critical mass of knowledge in the brain reached the saturation point and we finally got to the level where we understand what the author wanted to say in every paragraph.

That little hint about Kubernetes at 12:45 has me salivating for your explanation in the NEAR future. In the mean time, thanks for making this make sense in the most plain way possible. I get it. I finally get it. Thanks Dave.

I really appreciate you taking the time to make the videos. Even if I know the information, I still tend to learn a thing or two from you and always enjoy the show. Thanks again

Back in the day trying to run a VM inside of a VM on under Hyper-V would just error out ... But the same scenario under VMWare would pop up a very cool "You had to try, didn't you?"

When I saw the title "Docker vs VMs" (in the thumbnail tile, not on the video itself) I immediately thought VMS as in VAX/VMS. However, I wasn't disappointed by this video! 😊

Dave, thanks for the explanation. I'm learning how limited my education has been. "Drinking from the firehose of knowledge..." I love it! ❤️

i've been amazed how quickly Docker has been adopted and improved... in a 'past life,' i signed up for dotCloud and still recall how rapidly a container could be configured and launched... great work, Docker team.

I maintained our container stack (docker, containerd, runc) at a major linux distribution for about six months. I'm gonna keep this video in my pocket now, because it's a really good overview of some very technical topics that people tend to have misconceptions about (starting with containers are not virtual machines).

Compliments Dave. Among the most concise descriptions of this I have seen.

I'm not a SW engineer but had heard about Docker environments and had no idea as to what they were. Now seeing your video about Docker an VM, I now have a better understanding as to what they are. Many thanks.

This was great!. Clarifying and encouraging to make attempts. A blessing genuine.

Thanks Dave for the explanation. I’m a retired Windows Server engineer. I was responsible for maintaining VMs either under VMWare or Microsoft Hyper-V. It was good to be able to V-motion VMs or migrate VMs from one physical host to another in our VM farms so that a host server could be maintained, even rebooted without affecting any running VMs or applications. I don’t believe that same ability exists with Docker containers. So any application built in a docker container would need redundancy at a different level like Network Load balancing, clustering or something similar. Having to support many hundreds of VM servers with single instance applications running would mean planning for monthly patching and maintenance of the host at the same time of the host. While in the VM world the guest OS’s could be moved around to different hosts at will and we could patch the hosts at different times from the guests. Also any issues caused by patching would only affect one guest, so rolling back the patching of one guest didn’t affect all VMs like I’m guessing patching the Docker host might affect all Docker containers… But for sharing an applications between developers or end users in an enterprise, I do understand the benefits of having a smaller file size to share and move around . Thanks again for the technical information you share in these videos. Having been in the IT windows world, I find them being very interesting…

When you're 1-2 sec into a video and you gotta Like it ;) ! Really some awesome content Dave! Thanks for you stories also!

Hello Dave. I'm an autistic person too. I also struggle with the side effects of high iq. Could you make a segment on windows TSR(Terminate and Stay Resident) programs? For some reason I found great pleasure in making TSR''s that slept silently in the background back in the good old ms-dos days. Why did Microsoft introduce TSRs? Were they popular by other users? TSRs are kind of a strange bird. Who at Microsoft invented them and what was the primary use-case? Did you make / work on the TSR architecture? It was kind of magical that you could "terminate" a program but it was still in the background, and if you assigned a hot-key (say a function key) to it, the background program would immediately be back again without the initial load time.

Thank you for making a video on docker. Love your content!

Thank you for calling it "ooh boon too" like Ive been, instead of the cringe "ooh bun too" that they are trying to push.

Awesome…and I mean awesome explanation of the differences. My whole background has been with VMWare and HyperV. I’ve been trying to get a clear explanation of this precise thing and this has been the best and most clear.

Been looking into this so thanks for the information. I heard of Distrobox and wondered how the underlying technology worked. Mainly to see about trying to create a NixOS setup with Arch in a Distrobox for testing and being able to have an easily reproducible and backup.

Built a cluster of dell c6100s because I was inspired by you and similar channels. Keep up the great content.

Such a great video. You really made it easy to digest and understand from first principles. Thank you!

Thank you for this video. I am starting to learn about docker and this was a great overview.

I think Docker networking deserves a whole video. One thing that threw me off was that host names can only be used within the container even if the different containers are added to the same network.

There is absolutely nothing better than a bare metal hypervisor. Oh I miss those days, lol.

I saw VMS and read DEC. Miss that company.

Always informative Dave, I'm starting research on a new system development and this was excellent!

As a guy running a few servers in a homelab, the VM vs containers argument turned out to be peanut butter vs chocolate. Both are great, and sometimes they go well together. My particular professional use case leans heavily towards VMs - think ERP software best-suited for infrastructure supporting very large databases, and millisecond latency in certain scenarios can lead to critical output taking too long to reach the key stakeholders. My personal use case is leveraging containers to add few small workloads to make the day-to-day stuff like managing my digital media or just trying some new widget and destroying it if it doesn't meet my needs. Your conclusion was spot on, Dave. If it needs to scale one way or the other, pick the right solution.

Dave, this was one of my favorites of yours! Thanks.

Dave, Very well done summary of VMs and Docker. I will be sharing this video with people that need a good explanation. I have tried but I believe you did it better without getting into the weeds.

Your channel is a breath of clean air in todays youtube

Thanks for clarifying it in terms even I can understand!

I have to say that you are using a really good lens for your videos. The circle of confusion is really pronounced with a good focus and shallow depth of field.

Excellent video. In my job I want to push the docker approach and now I have more arguments for that :)

Another great video Dave! I use docker to deploy my application. One other advantage is roll back a release is easy. Just go to the previous docker version. Not that I ever have to do that.

Actually, you can also create a container without a declarative Dockerfile. You can build the container from a base image yourself by interacting with it using bash, for example, installing what you need manually using a package manager such as apt, for example, and in the end take a snapshot of the final container state into a new image that you can share. All without a declarative Dockerfile.

this is the video I been waiting for, Dave. Amazing

This is great content and very useful to me. You enrich with a lot of details and other informations.

Lets not forget about FreeBSD jails. It's a complete environment without the security burden of docker or the overhead of a VM. A little less convenient than docker but superior performance never the less.

David, man! As always great video about this fundamental technology for development. So much better explained than at class at my university. You can do a part two video detailing specific or known use cases for both technologies, and even get your hands dirty with some basic code, which would be really awesome. Then you should compare Docker vs Kubernetes. You are one of my favorite YT teachers. Thank you so much and have a nice day!

This is a very very good video especially for anybody who's maybe heard of virtual machines are containers but doesn't really understand what they mean

Really nice explanation! This is one of the interview questions I give potential systems engineers. It really is surprising how many people don't understand the tools they use every day.

To be absolutely real, Dave's dialogue on the recent lecture-esque videos like the opnsense video and this one have been really good Goes to show that the process keeps improving and I am ALL HERE FOR IT... giga banger and i will always hope for the next video

Man, I did some MS exams, with stuff about dockers, but still don't understand them.. in sentence #2 it's clear. Thnx!!

Great video. Thanks for taking the time to make it.

If you ever need to explain the difference between a container and a VM to anyone who is not an OS engineer take a snapshot at 8:30 . Your supervisor will think you are really smart. Gold quality content - thanks for sharing 👍

Looking forward to your kubernetes vs docker video. I really like the metaphors.

Nice and clear Dave. Would love a follow-up adding LXC's and venvs into the mix

Thank you Dave!

I knew most of this, but hearing an explanation of both reinforced some of my beliefs on how they worked and are different.

That was fantastic thank you you have connected so many dots for me! The perfect natural follow-up would be Dockers running in the kubernetes environment as you alluded to please consider that for your next project thank you so much you rock

I love your videos Dave, they're always really interesting and the insights into the goings on at Microsoft and your own vast knowledge of programming is fantastic, and I look forward to a notification of your latest upload. 😎😎

Thanks Dave. I was wondering on the differences. Since normally I have worked with Type 1 & 2 hypervisors.

Your explanations are so good!

ProxMox is not a Hypervisor; it is the frontend that manages Qemu, which is the Hypervisor underneath.

Had no idea what a Docker was, now I know. Thanks Dave!

thank you, Dave

Informative as always, cheers Dave!

Great discussion - thanks Dave

Another good vid Dave. Thank you!

Nice video, Dave. A little personal feedback, with stuff like this more visuals the better. Visuals helps me a lot when describing so many different technical nuances that I can pause and little it sink in more. :)

Another good use for VMs, running and testing different OSs.

Nice! Thanks for this vid, really underpins them both! Was excited for this vid and was not disappointed!! \m/

Thank you so much. I've used Proxmox for many years and even containers on it, but didn't realize that Docker was just a different brand of containers. I always thought it was a different VM stack.

I find this guy amazing to listen to. I am a retired Systems Architect which I did for a fortune 50 company for 17 years designing both Networks, Apps, MS Solutions and other crazy stuff with absolutely insane budgets. I did a lot of cool stuff. Now I have a different career, but still do the IT side of it for my family business now that I am involved in it heavily, I use IT to automate a lot of stuff using many different solutions, so I use a lot of tech. Guys like this make it fun to this day even though MS is a cancer. Thanks Dave, for these straight forward videos which I play on my second monitor while doing stuff. Edited for Grammar. Not sure what was wrong with me when I wrote this.

Thanks, Dave! That was a nice concise and clear explanation. Hypervisors I know well (ESXi/vCenter is my $dayjob with a dozen sites and hundreds of VMs across the globe.) I just spun up a new ESXi box from on a old work computer (i7) so that I can play with Microsoft AD and joining RHEL to the domain, something that I'll be needing for work and getting my RH certs. Since I'm going to be taking as many RH classes and certs as this 63 year old brain can stand, I know that Docker and Kubernetes are in my future. Your LED server will likely be one of my first attempts since you've also got me playing with ESP32. I've enjoyed your videos and hope you keep it up. Back when you were pounding on Win95 code, I was herding modems for Wolfenet, I'm sure we could tell each other stories.

Thank you for your clear explanation!!

Been wondering about this. Thanks for the explanation. I think I will have to watch this a couple more times before it all falls into place. Computing was pretty simple when I started in it in 1966. Even Linux was simple when I discovered it around 1995.

Well once more I blinked and was totally lost. Oh well I'll let my son study this, he would understand it. Thanks for reminding me why I gave up programing , heck my first exposure was with punch cards . Take care.

@Dave's Garage Thanks for another great and informative video. And I guess it might have made the video to long, but I would have loved to hear a bit more about the difference between running docker on Windows and Linux, since as I understand it it's quite possible to run linux "based" containers on windows but not vice versa. And I would love to understand a bit more of those "ins and outs" ;) Best regards.

This is another great video, keep em coming

Hey Dave! A channel called TheRetroRecall just did a deep dive installing original windows NT he has a shot at the start with boxed copies of most of your era Windows OSs. I thought it looked like a Daves Fan Club starter pack 😂

KEY THING: Docker images approach is to get both permissions and CPU/MEME requirements of our "containerized app" as low as possible. That's the main thing! And to separate immutable/mutable segments of all the shit.

Wow! That’s amazing and thanks for this knowledge

6:30 you can create a scratch docker container, exec a shell inside it and make changes, then run "docker commit" to create an image from the container. Just the same as you would with a VM and snapshotting. The Dockerfile is equivalent to the Vagrantfile of the VM world, it's just there to make it easier to track changes to an image in source control, it's not a necessary part of the infrastructure.

Great video, Dave! I've started using Terraform at work to spin up resources locally within Docker while also creating resources and VMs in AWS to interface with. I would love to hear your take on IaC and maybe your interpretation of pros/cons leveraging code for managing infrastructure. Cheers 🍻

Literally just spent all day learning about docker and then this came out. What are the odds?

I like this Peter Griffin part at the end! One day I will learn Kubernetes. For now, Docker Swarm seems magical!

That one was a brain melting experience. Thanks I loved it 😂

@7:59, and again @13:21 Dave, I have been searching high and low for that specific security aspect between Docker and VMs. I wanted the improved performance of Docker, but not with that risk. I want a sandbox of sorts, to keep various activities from seeing each other. Social media kept separate from banking, kept separate from gaming, kept separate from testing a download, etc. And even with social media, I want facebook kept 100% isolated from anything and everything (I stopped using facebook years ago, due to its aggressive spying / tracking of everything). I assumed that using separate VMs was the way to go, but was not sure if Docker was just as secure, and if I should learn Docker. Now I know not to struggle with learning Docker. I guess I was looking for a QubesOS style environment, without running QubesOS. Your video was exactly what I was seeking, for months. Thank you.

Great video on a relevant topic!!

Thanks for explaining, docker has been i little bit under my radar. Useful

I still remember the first time i recompiled gateway container on my production server. Been enhancing and polishing its docker file on my local dev server for weeks, catching and correcting compilation bugs before I finally had courage to pull and deploy it on production. Don't recall worrying that much since I was defending my phd thesis 😂

This was very exhaustive and handy video... I wish there were links that mentioned in the video though... But I'll subscribe to this channel for sure...

I'm liking this ahead of watching because I've wanted somebody to do a cross reference of these 2 in a meaningful way! \m/

7:59 regarding possible security exploits, I wouldn't quite say that a VM is fully isolated in all cases. Great explainer, I did have a little flashback to the days of using Thinstall/ThinApp for portable apps. Not quite the same as either a VM nor a Container, but somewhere in between.

cant wait to hear the kubernetes/orchestration piece! PODS vs CONTAINERS

Very informative. Thank you.

Doing both! VMs with docker containers

Having used VMs for a number of years as a software tester, they allow the complete environment and set configuration, which can be reproduced. Especially when I get a new drop of software, I just roll back to the snapshot of the os without the app installed (I don’t trust the app uninstall sometimes). Doesn’t sound like docker will do that same level of control.