AI FREE LEARNING ZONE

Ajouté : 2026-05-07

[00:00:00]all situated cuz they're always like the worst.

[00:00:08]YouTube chat is always the worst chat to be honest.

[00:00:13]They're always the most pissy.

[00:00:18]But who's ready to do one hour learning?

[00:00:24]Little to no AI because what's the point of learning if you're using AI?

[00:00:44]who's ready to jump into container month? Okay, [music] we have one hour to learn as much as we can about containers and then I will come in and I will present to you honest knowledge.

[00:00:59]>> [screaming] >> Three, two, one, go.

[00:01:04]What kind of start was that? Why did I do that?

[00:01:10]Anyways, containers. What are they?

[00:01:14]Let's start asking the questions. Who invented containers?

[00:01:20]What is a container? How do you use containers?

[00:01:28]Um, who, what, where, when, when when when do you use containers? Who, who, and when?

[00:01:40]You put stuff into them. Yeah. Tubware.

[00:01:46]Who invented the container?

[00:01:49]Who invented container?

[00:01:55]software.

[00:02:02]Oh. Oh.

[00:02:06]What is wrong with me today?

[00:02:14]Okay. Uh nowadays it's so hard to find things. Okay. So 199 1979.

[00:02:21]No.

[00:02:24]Within Unix, a so-called system called shroo brought to light. I'm going to sneeze as smooth of ways of providing a Oh my god. I'm going to rude.

[00:02:44]Hello, Chris XX.

[00:02:48]It probably I probably am having an allergy to the being outside, but I really hate the way my hair looks today. It looked so good yesterday, but my bangs don't stay overnight, and I refuse to style them before straight.

[00:03:23]Until [snorts] 2008, there were many solutions that worked around the concept of sandboxing.

[00:03:38]During that time, Linux containers got released. It provided new features like resource limitization and prioritization. Features like these were only known in the context of classic virtualization. Also, applications had an isolated view on the environment where they were working in. This was also very unusual compared to other solutions. It consolidated and isolated more against potential outbreaks.

[00:04:12]>> [snorts] >> Early versions of Docker use LXC as container execution driver. Okay. But Docker entered the market in 2013.

[00:04:23]They're there.

[00:04:25]That's how you know this was written by a human per.

[00:04:36]Every jail could consist of custom software installations and configurations. Besides that, there were aspects of isolating. [music] These sandbox features created the foundation for application testing and additional in identical environments. So free BSD jails until 2008.

[00:04:56][snorts] They got accepted. So Docker entered the market in 2013. But that doesn't mean the concept of a container.

[00:05:18]All these changes are also the story success story of Docker. They crafted a whole ecosystem of tools which are easy to use. Thinking of Docker Hub which is like a library of software solutions.

[00:05:30]um it isn't um that this doesn't make sense. It wasn't the range of features that made Docker so access successful.

[00:05:36]It was the functionality between tools.

[00:05:39]So as Docker was still pushing container virtualization on our local host, big companies like Google developed their own environments behind the scenes, Google realized early on that managing scale could be quite challenging. That is why they worked on Borg.

[00:05:54]Back in 2014, they released another name Kubernetes. It is part of the open source container orchestration through docker swarm exists although docker sworn exists as a counterpart. I can't talk today.

[00:06:05]Hello nilp pointer.

[00:06:14]Okay.

[00:06:16]containers reject as a part of it's okay to be okay whatever commuters commodity blah blah blah 2000 jail 2004 oh so the first first containers I'll say containers um why can't I Hello.

[00:06:47]Containers as an idea came about through chroot in Atlantics in the 70s, but free BSD introduced jail jails.

[00:07:11]DJ stream when Okay. No, I have my decks. I have my [music] decks.

[00:07:27]I could probably do a DJ stream tomorrow evening.

[00:07:32]I could probably I think I have time to do a DJ stream tomorrow evening because I have a hour booked off on uh on a co-working space to do it. But I could actually probably if I figure out how to do it tomorrow, I'll stream it. Okay.

[00:07:52]I'm not good though. In 2004, we saw the release of Solaris containers. No, no, no. Although it was similar to choo command and gave additional sandboxing features had additional sandboxing [music] features on top of chroot which then solar containers um created full application um environments 2004 2000 very y 2k page centered 2006. Google containers for isol isolating and limiting resource usage uh eventually became control groups. though 2008 Linux containers to provide virtualization and isolated Linux environments on a shared Linux kernel. So this actually so we want to say that that really 2008 was when the idea Hi goblin.

[00:09:21]2008 was when the idea of the container first came about. Hold on.

[00:09:51]I know I'm wasting time. Hello. Do hot dog flavored water.

[00:10:08]So stupid.

[00:10:13]me and my big ass forehead. So, we got our history. Cool. What is a container?

[00:10:19]What is containerization? It is Oh, wait. Did I save that? Yeah. Yeah.

[00:10:25]Yeah. Yeah. Okay. What is a container?

[00:10:29]What is a container?

[00:10:35]And then we also want to know how to use containers. What is the process of setting up a container? What happens behind the scenes happens on a technical level?

[00:10:51]Hardware level hardware o/OS level when deploying a container.

[00:10:59]Container.

[00:11:06]What is a container? Containerization is the packaging together of software code with all its necessary container.

[00:11:14]Container packages all software all code libraries, frameworks and dependencies together to allow isolation.

[00:11:38]This is that the software application with the container can be moved and run allows movement uh allows run on any env or infra independent independent of the OS containers are an alternative to coding on one platform or operating system.

[00:12:04]Wow. I really want to like call that quote out.

[00:12:16]What a great quote. Containers are an alternative to coding on one platform or operating system.

[00:12:33]Docker Docker Engine created a standard for containers with tools.

[00:12:45]In 2013, Docker engine created standards for using containers [music] via tooling uh via tooling and universal concepts to packaging which accelerated container uh interest.

[00:13:15]>> [snorts] >> Um shares hardware o OS OS level um share ability OS level ability to share OS kernel of host [snorts] negating the need for a separate operating system for each container allowing the application to run on the same infrastructure. We'll see in the next section. Similarly, developers can use the same tools when working with containers in one host environment as they'd use in another, which makes developing the develop which makes the development and deployment of containerization apps across operating systems much more simple. Containers versus VMs. That's a really great question.

[00:14:32]What's the difference?

[00:14:35]A VM is a virtual environment that functions as a virtual computer with its own CPU, memory, network interface, storage, and created on a physical hardware. Containerization and virtualization are similar in the fact that they both allow for full isolation of applications. Where the main differences lie are the size and portability. VMs are much larger than the two. Okay. So a VM has its own CPU, memory, network interface, storage created on physical hardware system.

[00:15:18]Containers much larger than containers.

[00:15:30]I don't care about you. Notion AI. Leave me alone. Oh my [ __ ] god.

[00:15:36]No one wants you.

[00:16:10]Um, which allows them to perform multiple resource.

[00:16:14]Oh, typically contain their own OS.

[00:16:18]Literally contain their own OS allows for more functionality.

[00:16:26]abstracts away the OS doesn't include anything except than the app itself and the running environment.

[00:16:47]Containers versus microservices.

[00:16:49]The containers are often used to package functions that perform specific tasks known as microservices.

[00:16:56]The containerization at the OS level.

[00:17:04]I wonder if there are any cute little diagrams. Oh, someone knew exactly what I was looking for.

[00:17:14][snorts] Delicious.

[00:17:29]Containers are executable packages.

[00:17:50]also contains runtime, system tools, libraries, and settings needed to run software.

[00:18:07]Containers allow developers to package and run applications in isolated environments. the process known as containerization. The technology provides consistent and inefficient means to deploying software across [music] I'm so ADHD today. I'm so sorry.

[00:19:28]There we go.

[00:19:30]Unlike traditional deployment methods, containers encapsulate an application and its dependencies in a container image. The image includes everything an application needs to run. Yes, we've already done that. They're much lighter because containers share the kernel but maintain their own file system. Oh, okay. Okay. Okay. Okay.

[00:19:50]They share the kernel but contain their own file system.

[00:19:58]Maintain They are much lighter and more resource efficient than virtual machines. I love this.

[00:20:19]I love that we're getting into the the technicalities here. I think this is a great diagram. [music] Yummy. Containers and VMs are both used to provide isolated environments for running applications, but they work in fundamentally different ways. The table below summarizes the differences between containerization and virtualization. It must be so annoying to watch me like do this and then also read through this and like learn at the same time, but like the music's really good.

[00:20:46]Container share the host systems kernel but isolate. So architecture- wise, containers share the host systems kernel but isolate the application from the system. They do not require a full OS for each instance, making them more lightweight and faster to start than VMs versus VMs which include not only the application and dependencies, but entire guest OS. This runs on hardware powered by a hypervisor which sits at top the host physical hardware.

[00:21:17]VMs are isolated from each other and from the host system providing a high degree of security and control. So I think one of the things that always kind of confused me is like what is a hypervisor and a virtual machine in general and I I really want to call out here that's something that I think will add some clarifying language is like for example when you run um virtual box virtual box is a hypervisor and that took me like someone had said that to me once and I was like oh like that's what a hypervisor is. So virtual box is like a hypervisor versus Docker is like some complete thing different thing. The way I've always also seen it is like you can't open a Docker container and like move a mouse around in a Docker container, you know, but you can do that in a virtual machine. And I think like that kind of Cloudflare wants me to verify that I'm a [ __ ] human.

[00:22:16][ __ ] I'm not.

[00:22:19]My current favorite fake lord to spread to my friends is that I spawned in at the age of 11. I just like appeared on Earth.

[00:22:30]And I've just been like telling them.

[00:22:31]They're like, they were just like, "Oh, what about when you were a kid? I just like, no, I just like showed up at 11.

[00:22:38]I just spawned onto Earth at 11. Just like showed up in a solar flare. just like showed up and my parents like that's our kid now.

[00:22:48]Why can I not exit this? Hello. I verified that I'm human.

[00:23:01]How does containerization work?

[00:23:03]Containerization involves encapsulating container escape room. Our um our lovely Wait, wait. Um, wait. No, no, no, no. Was it >> [snorts] >> What? Ian Coldwater was I'm pretty sure the first on the first team to escape. Yes. Okay.

[00:24:04]Ian Coldwater was the first person on the planet to escape a container on a mainframe.

[00:24:14]And we love Ian Cold Water. Ian Cold Water is a great person. They have been nothing but extremely supportive of me.

[00:24:20]So, [clears throat] wait, did Net Spy did Ian Coldwater work at Net Spy? You're kidding.

[00:24:34]the first mainframe container breakout, which is super cool. What does that mean to me? I don't know what it means by mainframe, but do you know the look it up baby tweet?

[00:24:46]Of course, I was on Twitter when that happened. And the way Twitter just like it was amazing.

[00:24:56]I don't want to use threads. Ew. Yikes.

[00:25:01]E.

[00:25:03]Okay, this is AI generated.

[00:25:08]Of course, I know the look it up, baby.

[00:25:13]I love Ian Cold Water because like no one knows that they did all this stuff.

[00:25:17]And then for the context to look it up, BB tweet is this amazing thing where Ian Cold Water had a man um there was some man on Twitter like being a piece of [ __ ] towards Ian Coldwater and they were like, "Well, if you read the keeper, you would know like blah blah blah blah blah blah blah. And then Ian was like, "Look it up, baby. My name's on it." And then Emma was just like, [screaming] like literally Ian Cold Water just like absolutely boom.

[00:26:10]Just amazing.

[00:26:16]I wish we preserved like the full conversation because after that point like Ian Coldwater just made their like it was amazing delicious such good drama to watch.

[00:26:29]Um anyways uh key points of a container container engine this is the software that provides the runtime environment.

[00:26:35]Okay. So key parts of a container container um container parts the engine software that provides a runtime envir this this um this is like docker rkt etc uh container image the image uh includes all the components for the container to run.

[00:27:13]Rune registry storage and delivery system holding container images and then orchestration tools.

[00:27:35]um management uh multiple containers uh name spaces I feel like in croups these Linux features are used to isolate containers used for container isolation but I feel like the name spaces are used by the container engine complexity and management this is really good. Server watch kind of slate on this honestly. Good job server watch. Um I've also realized that we never got the um red hat.

[00:28:25]Uh the red hat history of a container.

[00:28:30]There we go. We want this. I know probably like, "Oh my god, Ally, showing your history, your browser history like live on stream." Girl, this this Chrome instance only gets used for streaming. So, there's nothing to hide there.

[00:28:51]Let's see. Let's get deeper. Let's get deeper. What is a container?

[00:28:56]Containerization architecture.

[00:28:59]Let's see. Containerization at the kernel.

[00:29:10]Architecting containers part one.

[00:29:12]Understanding user space versus kernel space matters. Perhaps you've been developing containerbased application infrastructure. If so, you most likely understand the value that containers can provide to your developers, architects, and operation teams. In fact, you've been reading up on containers and are excited about exploring the technology in more detail. However, before diving head first into the discussion, all processes, okay, while containers are sometimes treated like virtual machines, it's important to know unlike virtual machines, cont a kernel is the only layer of abstraction between programs and the resources they need access to.

[00:29:45][clears throat] Am I choking?

[00:29:52]Um, as containers are processes, they also make system calls.

[00:29:57]Amazing.

[00:30:01]So you understand what a process is and that containers are processes. But what about the files and programs that live inside the container images? These files are programs make uh and programs make up what is known as a user space. When a container is started, a program is loaded into memory from the container image. Once [music] the program in the container is running, it still needs to make system calls into kernel space. Can you Running a guey application in Docker containers, a step-by-step guide. Docker has revolutionized how we develop, ship, and run applications, making containerization a breeze. While Docker is renowned for its server and command line applications, running guey applications within Docker containers can be a bit tricky. In this guide, I'll walk you through the steps to run a guey application from a Docker container using Firefox as an example. [music] You could do it.

[00:31:16]So you start Docker, create a Docker and open a Docker file.

[00:31:26]Run the Docker container with Guey support. To run a Docker container with Guey support, you'll need to configure X11 server access.

[00:31:41]Here's a breakdown of the docker run command.

[00:31:53]It allocates [music] pseudo tty and keeps standard in open for interactive mode. Automatically removes container after it exits, keeping your system clean. So display sets the display environment variable inside the container to match your host machine's display. Oh, that's probably the big dash e -v mounts the x1 Unix socket allowing the container to communicate [music] with the xserver on your host. What is an xserver? My firefox specifies the docker image to run. Understood.

[00:32:27]Okay.

[00:32:30]So running a guey application inside docker in containers and balls. So you can run >> [snorts] >> You can run guey programs, guey programs via Docker, via containers.

[00:33:02]It's just not a popular use case.

[00:33:12]User space refers to all the code in an operating system that lives outside the kernel. Most Unix like packages operating systems come prepackaged with all kinds of utilities, programming languages. This is called userland.

[00:33:23]Userland applications include programs that are written in C, Java, Python, blah blah blah. In a containerized world, these programs are typically typically delivered in a container image format such as Docker. When you pull down and run a Linux 7 container image from the Red Hat registry, you are utilizing a prepackaged minimal Red Hat Linux 7 user space which contains utilities such as bash o GP yum yum.

[00:33:52]All user programs function by manipulating data. But where does this data live? This data can come from registers in the CPU and external devices.

[00:34:09]User programs get access to data by making special requests to the kernel called system calls. User programs examples include allocating memory or opening a file. Memory and files often store sensitive information owned by a different user. So access must be requested from the kernel through the OS. The kernel space provides abstraction for security hardware and internal structures. The open I lost focus for a second and I lost the difference.

[00:34:50]Okay, so user space versus kernel space.

[00:34:52]I feel like this is a little too Let's see where this leads. So, this is in 2015. Wow, this is in 2015. People are so cool.

[00:35:14]Oh, whoa. This guy's name is Scott McCarthy, but his like handle is Father Linux, which is like what a crazy name to keep.

[00:35:26]This is the essence.

[00:35:28]The essence of containers.

[00:35:31]Keep going. Do we have enough time to read all this is the question. We have 25 minutes. Not really.

[00:35:39]We will save her.

[00:35:47]We only have an hour.

[00:35:50]What is a container? What is a container engine?

[00:35:58]A container engine is a software tool that automates container engine.

[00:36:21]These container engines package an application's code ensuring the application because so the container engine performs several vital functions.

[00:36:30]Uh at their core they create, manage and run containers. Create, manage and run containers which are readonly templates built from a set of instructions. So container images Read only set of instructions for what to include in a container, but the engine is the one that like goes out and gets it. I'm going to sneeze again. Oh my god.

[00:37:19]I said, "Oh my god, Sneeze McGee."

[00:37:26]They allow developers to establish consistent reproducible environments thereby streamlining the process of developing, testing, and deploying applications.

[00:37:35]Um, is this a general concept or language specific? Is the idea of a container image [music] a general concept or language specific? I believe that a container image is a general concept in the sense that for every kind of container you can run they produce a container a container image which then a container engine can go and read and get information about and then run the container. I if I remember correctly container images are um you can you only can generate once in the sense that like say I make a container image or say I do something that I want to make turn into a container so then I set the image I create the image that is that image I can never mutate change or edit that image if I want to update that I have to make a new container image How do container engines work? Oh, here's the juice, y'all. This is what we were looking for. Amazing.

[00:38:53]So, container engines, they have a damon, three parts.

[00:39:04]three parts. Damon runs on host machine overseas operations, listens and then we have the client, the CLI tool that um issues commands to the Damon.

[00:39:29]I want to learn too. Yeah, we could publish links one day. And then the runtime which is um responsible for running the containers.

[00:39:48]creates and manages container processes by being the interface between the um to the operate the host host OS OS amazing container architecture overflow overview. Oh, this is what a beautiful image. What a great image. Whiz Purr like come in gorgeous. What a great image. Popular container engines amazing. We know Docker uh Kubernetes is for multiple oh cryo.

[00:40:32]Cublet Open Shift is the Red Hat instance.

[00:40:37]Um these are the different cloud ones.

[00:40:42]Security implications. Amazing.

[00:40:53]Um, anatomy of a container engine.

[00:40:58]Anatomy of a container image.

[00:41:05]Here we go. Here we go.

[00:41:14]A container image is a lightweight standalone executable file package containing all the components. Um the container image comprises of the root file system and some configurations together the file system bundle. The root file system is the contents of the container. At the same time the configuration information gives instructions on a runtime parameter that it should be set up by default when running the image. For example, suppose an environment variable is specified to the images configuration. It will be defined for the container process when it runs.

[00:41:45]The container engine or the runtime is a software responsible for managing uh containers and their entire life cycle.

[00:41:52]It plays a central role in container orchestration and interacts with other components on the container ecosystem.

[00:41:58]container engine such as docker containers [music] rkt perform the container runtime okay the engine is the runtime the container runtime typically resides on the host system where the containers are to be run and interacts with the host operating system leveraging kernel features like the namespace and croups for isolation and resource management. The runtime also communicates with other container components such as the container images and registries to fetch and manage images required to create container instances. Developers or container orchestration like Kubernetes, Docker Swarm usually invoke the container runtime. Developers can call the runtime directly during development and testing during the command line interfaces using the command line interfaces.

[00:42:52]At the same time, orchestration tools manage container deployment, scaling.

[00:42:57]Okay.

[00:43:08]So, what bothers me here is that it only talks like does does do do containers do containers exist for Windows?

[00:43:22]Is that like a dumb question?

[00:43:25]Yes.

[00:43:29]I just think it's really funny because like they're all like, "Oh, the Linux name space." And I'm like, "Y'all, there's more to the world than Linux."

[00:43:38]And I I imagine that not many people are using things [music] like um I I imagine that using things like um not Linux using things like Windows is not very practical for actual containerization.

[00:44:02]You know, like I'm sorry, who's actually deploying a Windows server?

[00:44:08]like look me in the eyes and tell me that you're using a Windows server, you know.

[00:44:15][snorts] I use container with Docker to run Leta code with a local LLM. Windows server people get paid a lot because nobody likes it. Exactly. Because Windows sucks.

[00:44:39]I had to say it. Windows sucks.

[00:44:47]The UTS namespace isolates host name and domain name, allowing different containers to have their own host name and domain name. IPC name space control groups croups blah blah blah. I mean this is truly like a fabulous this is really great.

[00:45:12]Lots of great resources about this. I feel like look me in the eyes and tell me. That's what I always want people to do. Just just I just want you to be able to like look at me in the eyes and say, "No, you're right. No one does really care about Windows servers.

[00:45:36]Containers is a pretty research topic."

[00:45:38][music] Yes, it is.

[00:45:41]I thought programmers were all massochists. Anyways, am I >> [snorts] >> I hate this [ __ ] ass font.

[00:46:07]This like [ __ ] ass font. Like what are we 12?

[00:46:12]This is genuinely such a [ __ ] ass font.

[00:46:17]What's the the the the like um platform everyone uses like Excalar or whatever.

[00:46:23]The most [ __ ] ass font ever. Just use Ariel.

[00:46:35]Just use Ariel.

[00:46:37]It's like this is like the most [ __ ] ass font ever.

[00:47:00]I feel like we could do an entire learning set just on container engines, which maybe we'll do. Maybe we'll do just an entire learning session because we have container month.

[00:47:12]You got an ad for Azure DevOps and that's never happened in your life. Oh my god. I didn't put anything about doing DevOps on my channel.

[00:47:23]Wow. Okay.

[00:47:30]Okay. So this is a write up to explain container image format as it's described by the OCI image specification and to a lesser extent the OCI distribution specification. This post will focus on well-known concepts like uh image layers, image configurations, image image manifests and image indices. We'll also talk about image ids and image digests and how images are stored and addressed locally and in registries.

[00:47:56]Traditionally, the idea to show why each of these parts is needed, when it's used, and how the parts work together instead of just using describing them in dry terms, rehashing the specs.

[00:48:10]Let me mention something else. Mention like I don't know, I feel like like IBM AI something something. There's probably some good ad there. By the end of it, you should be able to explain how the same Docker pull command ends up fetching different images. See? Wow.

[00:48:26]Look at this. Wow. People write great stuff.

[00:48:32][clears throat] Okay. At its core, a container image is an archive is an archive with the application, all of its direct and transitive dependencies, required OS packages, and container execution configuration inside. In other words, okay, the better. Okay, there's so much to read here.

[00:48:52]Is this font better? Yes, this font is so much better. It's less [ __ ] ass. I still hate that font.

[00:49:00][snorts] I feel like I should tweet that like tweet hot take. The Scala Draw font is the most [ __ ] ass childish font ever.

[00:50:39]Okay, I tweeted it. I just I want to start a war.

[00:50:44]I gave two options, Ariel and Atkinson [music] Hyperledible. If you don't know about the Atinson Hyperledible, it's literally designed for like being It's literally designed by the [ __ ] Braille Institute for readers with low vision and improve comprehension.

[00:51:03]Okay, you don't need a [ __ ] font like that one.

[00:51:12]Um, OCI images is an inherently single platform construct. Given image configuration, you should always be able to tell the target platform. In addition, an application's runtime.

[00:51:25][music] Um, the configuration also references. I'm more of a cal C collabor. Yeah, go for it. Just anything but that base font. So, [ __ ] ass. So, it's so infantilizing.

[00:51:47]Now when you have another application based on Ubuntu, you don't need to do duplicate. You don't need to duplicate the base layer. Just prepare another diff. I really want to save this and do like a deep dive into container images.

[00:51:59]What if for container month we do uh we do security and then we do deep dive images plus engines and we can make that part two.

[00:52:14]Bada bing bada boom.

[00:52:23]Day one containers top level cuz we only have 9 minutes left.

[00:52:29]Thank you for the follow, both of you.

[00:52:31][clears throat] I keep fluctuating and sticking at 12,000 and it's really [ __ ] hard and I wish that I would just keep going up cuz so many of y'all keep unfollowing. It's really annoying.

[00:52:45]Let's see. I think that just starting with the idea of so search prompt Anatomy of a container.

[00:53:23]um software. [ __ ] Let's go to images. I feel like images is always a great place to jump in because then you can get so much.

[00:53:35]Well, actually, no. We know what comes up with a container is like the entire idea of this, right?

[00:53:44]There's no anatomy of a container because a container is actually multiple parts.

[00:53:54]The container manages this, right?

[00:53:58]The container is the actual running part of it. Yeah. The container is the actual running part of it. So each container is the actual running part and is what is operated and managed by [music] the engine right and then we have the engine which actually runs it and the image which actually builds it. So the container is actually the hardware part of or not the hardware part of it is the software part of it. What do you have against AI? A lot. I'm scared of it. I'm frightened of it.

[00:54:33]AI scary. AI so scary container diagram.

[00:54:59]Once you understand how your system fits into the overall IT diagram. Nope. By containers have become standard packaging and development. We have five minutes left. Deep dive into Docker containers. We already kind of understood it, but here we go. Here's that same idea of like there's the orchestration, the engine, and then the runtime. But the container is the actual thing that is running on the computer.

[00:55:23]The engine is what manages it, and the runtime is what runs it. The engine is what allows that container to run.

[00:55:32]It is a standard unit of software.

[00:55:34][music] I like that term standard unit of software.

[00:55:40]Standard unit of software.

[00:55:46]I think that's a really great term.

[00:55:48][music] Standard unit of software.

[00:55:51]That's a cluster architecture.

[00:55:54]Let's see. C4. No.

[00:55:59]research gate. I am a human.

[00:56:07]No container service diagram. Nope.

[00:56:33]What is this? No.

[00:56:37]Context containers, I guess. Yeah. Like what? It's hard to look up like a container architecture because it wants to show you like a literal [ __ ] shipping container.

[00:56:50]I want to show you a literal [ __ ] shipping container.

[00:57:19]So [clears throat and cough] the container contains the app and the binaries and libraries and that's the container. But then what about it's saying like it has all of the like runtime stuff and settings needed to run it and allows.

[00:57:39]Okay. So packages all the code. So it doesn't containers don't actually run.

[00:57:44]Containers don't actually run. The engine operates the container. Is that the right?

[00:57:57]Hold on. We have 3 minutes left.

[00:58:03]A practical introduction to container terminology. This is father Linux again.

[00:58:08]This dude cracked Um, when you start command, the container engine unpacks the required files and metadata, then hands them off to the Linux kernel. Starting container is very similar to starting a normal Linux process and requires making an API call to the Linux kernel. This API call typically initiates extra isolation and mounts a copy of the files that were in the container image. Once running, containers are just Linux processes.

[00:58:32][music] Okay, so they are technically containers technically just system processes. when running.

[00:58:55]People will use the word container to refer to both but the running container and also the state on the disc even when it's not running is you can ask is the container running? Yes.

[00:59:10]Basic vocabulary. Basic vocabulary.

[00:59:13]Container [music] image format.

[00:59:14]Container engine and container.

[00:59:16]Containers exist within the operating system. Containers is the runtime instantiation of the docker of the container image. A container is also a standard Linux process typically created through clone.

[00:59:28]Containers are often isolated further.

[00:59:31]So it is actually what is running on the house but also the p the wrapup of the pro the things needed to run it right.

[00:59:52]I feel like now is like the question that we can ask AI pet containers.

[01:00:13]Docker doesn't provide the OS. The process running within the container in Docker uses the host kernel but the container itself provides all the user space content. So lib standard library binaries and such. Docker relies on quite heavily on parts of the Linux kernel for the containerization. So when it runs on non Linux OS, it is normally installing a Linux VM under the hood and [music] transparently proxying your interactions. It's highly unlikely that large containers blah blah blah. How does Docker work? We're not there. Shut up.

[01:00:52]Yes, we have seen this. Um containers don't run on Docker for that matter.

[01:00:57]They don't run on Kates either. They run just like regular programs on an operating system. But there's another common problem going on. Way too far.

[01:01:03]Many drawings only show containers running on operating systems with no sign of Docker. Um, let's clarify what we were talking about here. Oh, we have a timer.

[01:01:13]We got a timer.

[01:01:16]I feel like we learned so much. We have so much. We've [clears throat] learned so much.

[01:01:24]Anyways, um we have a lot there.

[01:01:42]We have a lot there to kind of break down.

[01:01:45]Um so, you know what it means?

[01:01:49]It's time to make the slides.

[01:01:52]I have to think of a good theme.

[01:01:57]What brain rot do you want?

[01:02:10]I love fridge restock brain rot. I love fridge restocked brain rot.

[01:02:16]I'm not going to lie. I love fridge restocking brain rot. Oh, just really does something.

[01:02:39]Oh, wait. What?

[01:02:45]Oh, this is only Oh my god, it's only just Tik Tok videos. Oh, this is sick.

[01:03:03]I love giving y'all. Okay. Hello.

[01:03:05][music] We need one more um brain rot video. [clears throat] What kind of brain rot do you want? like um brain rot one hour skippy toilet compilation. Sure.

[01:03:55]We are right now doing a 1-hour learning challenge and I have to go take 15 minutes to make a presentation or 30 minutes to make a presentation and I have to decide what I'm showing you for brain rot. Um, one hour petting [music] cat compilation.

[01:04:17]Oh, one hour funny animal videos.

[01:04:21]That's fun.

[01:04:50]So, we need 1800 seconds. So, I have 30 minutes to make y'all a presentation.

[01:04:57]During this time, I'm going to turn up the music. You all have some brain rot and you could come hang out while I make slides about containers.

[01:05:09]Three, two, one, go.

[01:05:19][music] [music] >> [music] [music] [music] [music] [music] [music] >> Hey. Hey. Hey.

[01:06:19][music] [music] [music] [music] >> [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] >> down.

[01:08:24]Hey >> [music] [music] [music] [music] [music] [music] [music] [music] >> Hey. Hey. Hey.

[01:09:46]Hey, hey, hey. [music] [music] [music] [music] Hey, hey, hey.

[01:10:18][music] [music] [music] [music] Hey, hey, hey.

[01:10:52][music] [music] >> [music] [music] [music] [music] [music] [music] >> Heat. Heat.

[01:11:59][music] [music] [music] Hey, hey, hey.

[01:12:27][music] [music] [music] >> [music] [music] [music] >> I need [music] [music] to >> [music] [music] [music] [music] [music] [music] [music] [music] [music] >> Hey. Hey. Hey.

[01:15:04][music] [music] [music] >> [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] >> Hey, hey, hey.

[01:18:00][music] [music] [music] >> [music] [music] [music] >> Hey. Hey. Hey.

[01:18:53][music] [music] [music] >> [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] >> Hey, hey, hey.

[01:22:07][music] [music] >> [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] >> Hey. [music] [music] Hey. Hey.

[01:25:25][music] >> [music] [music] [music] [music] [music] [music] >> Heat. Heat. N.

[01:26:21][music] >> [music] [music] [music] [music] [music] [music] >> Hey, hey, hey.

[01:27:32][music] [music] [music] [music] Heat. Heat.

[01:28:05][music] [music] [music] >> [music] [music] [music] [music] [music] [music] [music] [music] >> Heat. Heat.

[01:30:05]>> [music] [music] [music] [music] [music] [music] [music] [music] [music] [music] >> down.

[01:31:41][music] [music] Hey >> [music] [music] >> Hello. [music] [music] Hey.

[01:32:27]>> [music] [music] [music] [music] [music] [music] [music] [music] [music] >> Hey.

[01:34:04][music] Hey. Hey.

[01:34:19]>> [music] [music] >> Okay, are y'all ready? Hey Siri, turn off garage.

[01:34:56]Welcome. Are y'all ready for the container presentation?

[01:35:05]>> [cough and clears throat] >> Oh my god, I got so I I'm at the family table, guys.

[01:35:17]Wait, this is so exciting, guys. Wait, this is so exciting. Look, I'm at the family table.

[01:35:31]This is really cute.

[01:35:37]Can you see it?

[01:35:41]No. Okay. Anyways, okay. Who's ready to learn about containers?

[01:35:47]I'm here to present to you on the concept of containers because today's learning one hour learning challenge was containers.

[01:35:57]Why do I keep saying the word containers? We're going to say it a thousand times more during this entire presentation. So, I hope you're looking forward to it. Let's jump into it, shall we? I love this theme. I think this theme is so great. It's so cute. Okay.

[01:36:10]Sorry. I'm really excited about it.

[01:36:12]Okay.

[01:36:15]Okay.

[01:36:19]Why am I likeexe not working? Whatever. Anyways, let's talk about containers. That's too high up on the screen. Anyways, let's talk about containers. So containers are first born from the concept of Linux CH root in the 70s which enabled different processes to be run on Linux as different instances on a Linux operating system that originally first came out in the 70s.

[01:36:47]Containers technically has a very long and seasoned history, but the first real idea of sandboxing with these different processes came around in 2000 with the introduction of free BSD jails. In 2004, a full application environment was announced. These were called Solaris containers. And then in 2006, Google created containers for isolating and limiting resource resource usage. But these containers that Google created actually became the idea of control groups though. So a little bit different from containers. And then in 2008 was when the real idea of containers came where Linux containers were invented or LXC that create virtualization and isolation on Linux environments with Linux environments on a shared Linux kernel.

[01:37:43]These eventually evolved to become Docker containers which were announced in 2013. Now technically containers as you can see existed before Docker containers as Linux containers. But the really big difference of what happened at in 2013 versus what happened in 2008 was that these Docker containers actually created better tooling around the concept of isolated um isolated virtualization and environments that made it easier to adopt the concept of containers across all these different companies. the Docker the Docker creation of Docker tooling around containers made containers explode.

[01:38:27]So we read this really great quote that I quote that I wanted to call out here.

[01:38:39]Containers are an alternative to coding on one platform or operating system.

[01:38:46]We see that That is because containers enable people to run on any infrastructure or or environment dependent of the operating system. They come in all shapes and sizes. As I said, they can run independently of the environment or infrastructure they're developed on and essentially are the idea of an executable package. Now containers as a term is said very very loosely but at the same time very specifically. When you and I think of containers, we probably think about Docker and Docker containers. But instead, what we really need to start thinking about is a container as a standard unit of software. A standard unit of software.

[01:39:36]because Docker is not the only company that creates container tooling.

[01:39:44]Okay.

[01:39:46]So then we want to know what's in a container. What actually is in a container and the concept and the standard unit of a container because we are now want to treat containers as a standard unit of software. A container contains things like the actual code of the software that needs to run, the actual libraries of the software that needs to run, the frameworks of the software that needs to run, the code that needs to run, the dependencies of the code that needs to run, the system toolings needed for the code to run, and the system settings needed for the code to run. It doesn't contain everything needed for the code to run in the sense that it doesn't contain like OS kernels, things like that, but it contains everything on top of that that is needed to run independently.

[01:40:35]But speaking of OS, you're probably thinking, "Wow, that sounds kind of like a VM. VMs operate separately." Uh, but the difference between what a do a a container has See, I almost said a Docker container. The difference between what a container has and a VM is that VMs have things like CPU, memory, network interfaces, and storage all in its beautiful little wrapper.

[01:41:00]VMs are much larger because of that.

[01:41:03]They can contain things that aren't necessarily needed to run the VM and the software that's on the VM. Instead, they contain everything that's needed to run plus the software that needs to run. A container only contains everything that is needed to run and is much smaller.

[01:41:21]Don't it's much smaller than a VM.

[01:41:26]And I wrote this and now I'm seeing I don't really understand what I wrote there. Containers don't think OS.

[01:41:38]I wish I could remember what I meant by this at all. I wish I could remember. But I think something that's really cool about um containers that we learned today is that generally I used to think of something as like a VM versus a container. And the way that I used to think about a differentiator is like VMs had gies and containers don't. But it turns out that you can actually hook up containers to displays to show what is running on the container. So technically you can run guey dependent programs and interfaces on a container. Learn that today. So jumping in a little bit further to see that breakdown a little bit more. As you can see over here, there's a lot more happening on a VM versus a container. A VM for each VM that exists there contains there is an entire separate operating system that is contained in the VM. that makes up a huge bulk of what a VM stores a lot of stuff about the operating system and things like that and they're run by hypervisors that can run these separate operating systems as independent programs. The thing about containers is that they don't have that operating system information all that knowledge and whatever is needed to run the operating system. only contain just the information to run it on the container engine. Essentially, all of these do run on the host operating system and the infrastructure, but instead they're still operating separately. They're different things.

[01:43:17]Containers don't contain information about the operating system they're running on. They just contain the information about what they need to run on the operating system.

[01:43:30]Understood.

[01:43:34]Any questions?

[01:43:36]That's the entire presentation. We sent in an hour and we made this sort of presentation. I know it's because we spent an hour going into other things like um what the the components of an engine and the image and the registry and I was like wait pause those can be their own separate studies you know so I thought that would be a little fun to put as their own separate in container month so as we do every time.

[01:44:22]As I do every time, vote in the poll for how I did.

[01:44:26]One is I got everything wrong and two is I am a container god.

[01:44:31]You know, I don't think there will ever be a point where I get like a five on something. But go vote in the poll if you're still present. Honestly, a three is good. Go vote in the poll. Let me know how I did because I got to get to work.

[01:44:52]Honestly, a three four makes a lot of sense. A three. A three. A three to four makes a lot of sense for how I'm feeling on this.

[01:45:02]We hang out. We wait. We learn. We conquer.

[01:45:18]A 10. Thank you. But it's only out of five.

[01:45:24]a four. I'll take it. Feel really good about that. But that's exciting.

[01:45:29]Anyways, fancy. Look at this. Using the green screen properly, a girl can grow.

[01:45:36]Anyways, [clears throat] uh let's quickly film an outro. So hopefully if you're watching this, you enjoyed this and you learned something about containers. I know I did. But we are continuing container month or container week, container, however long it takes to release these episodes. But if you enjoyed the show, please be sure to like, comment, subscribe, and let me know if there's any topics or things that I got wrong on here. Let me know in the comments because I know that there's probably going to be some DevOps people that are like, "You got everything wrong. You got everything wrong." Which is fine. But be sure to like, comment, subscribe, follow me on Instagram. I'm really trying to hit 100,000 followers on Instagram by the end of the year, which may not happen, but every follow counts and I appreciate you. So, thank you so much for watching. Good luck, have fun, and don't die. Bye.

[01:46:21]Yay. Amazing.

[01:46:24][clears throat and cough] Another YouTube video filmed. I do take a lot of this and turn it into YouTube videos, but I do really need to go to work now because I am 30 minutes late already.

[01:46:32]Um, so let's drop you off somewhere.

[01:46:48]y'all can go hang out with study time today. She's actually working, so have fun learning and studying and being good today. Okay.