Docker 101 and How do containers work?
Everyone is using containers and talking about containers. Except those for whom it hasn't "clicked." Obvious to some and unendingly frustrating to others, containers are changing how we build and deploy software. As part of my ongoing 'Computer Stuff They Didn't Teach You' Series on YouTube, I explain Containers and Docker in about 30 min, with lots of demos and slow, deliberate examples.
Please do check it out and subscribe as I'll be doing Kubernetes next.
I hope you enjoy it! Please subscribe to my YouTube and explore my playlists and recent videos!
Sponsor: Suffering from a lack of clarity around software bugs? Give your customers the experience they deserve and expect with error monitoring from Raygun.com. Installs in minutes, try it today!
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
Another great video as always. Apart from containers and Docker, I learnt that there's a way to quickly snap shot the screen/window, zoom into the image and put up arrows and rectangles. You did this between the 22-23 minute minute mark when talking about port mapping the Nginx docker image.
How did you do that?
Thanks!
I can see some advantages of Docker over App Service, such as making the environments consistent everywhere. But, deploying and running on App Service is a really great developer experience, so I've never seen any driving reason to switch to Docker (sure, I know App Service will run containers). I also look at Kubernetes as a layer of complexity that I don't want to think about. Sort of, if Docker simplifies, then Kubernetes is the brain tax that I pay back for that simplification.
So, other that Docker being really cool and bringing consistency of behaviour, how would using Docker improve my developer experience over "just" deploying out to App Service from AzDo, please, Scott?
Thanks!
Comments are closed.
With respect, "everyone" in this context constitutes less than 0.001% of people on Earth.
Things like Assassin's Creed, Call of Duty, Age of Empires, AutoCAD, Photoshop, 3ds Max, Microsoft Office, Visual Studio, most video games, most productivity software, most entertainment software, and many, many, many other things do not run inside a container. People who never user containers include gamers, creative artists, engineers, designers, architects, film makers, most software developers, lawyers, managers, chefs, policemen, postmen, politicians, consumers, and anyone else who's primary computing device is a workstation, tablet, or smartphone.
We used to dream of a computing worlds in which security is established by containerization instead of antivirus vendors who always play catch-up with threats. Oh, well, one can dream, right?