#5 - Understand how Docker works in 5 mins ⚡⚡

in this lecture we'll be talking about Docker architecture so we have already discussed about the docker architecture in our last lecture while we're discussing about the docker containers and how the docker containers is entirely different from the virtual machine that we always use so just to recall it once again you can see that our machine can have a CPU architecture of x66 or x64 arm and it will also have a memory like a ram and also it will have an hard disk or pcie or whatever Express that you use and we also have network connectivity with machine so we'll have all these in our bare metal machine and then we will have an operating system installed in that machine it could be Windows Linux or Mac operating system but on the top to run the containers we will have Docker engines and then it's going to spin up the containers for you something like this and this exactly we saw how the docker CLI is going to do that from the command line it sends a rest request to the docker demon and then it's going to spin up the containers for us something like that but there are even more processing going on in the docker demon not just like doer demon is going to spin up the containers for us something like this rather the architecture is going to look something like this behind the scene so this is what happens under the hood while a CLI is going to ask for creating a container or pulling an image and deleting an container you're going to be going through these many process you're going to be sending a request to the docker demon and the docker demon is going to then call a container D and this container D is going to call a run C and this run SE is going to call the container runtime and then it is going to spin up those containers for you something like this and this container runtime is going to manage the name spaces and C group or otherwise call as the control groups which is going to control the isolation of the containers to be running in their own process so that it won't interfere with another containers so that's what the name spacing is and the C group is going to be the control groups which is going to be used for controlling the resources that is being used within each of these containers by sharing the resource from your operating system as well as from your memory within your machine so I mean this name space and c groups are something is coming from the Linux operating system directly and that's what is been used by the docker itself and you can see that there are so many information here like container D and runy well container D is an industry standard container runtime which is a core part of Docker ecosystem right now and it now a standalone project as well and most importantly this is now a project within the cloud native Foundation or cncf and it is designed to be a lightweight and robust solution for managing container life cycle from image transfer and storage of the container execution and supervision so this container D does quite a lot of things under the hood and not only that it does the container life cycle management image management storage and networking runtime support Eventing and monitoring so it does quite a a lot of different operation and there's a big story behind this container D I will quickly show you on the container d project page in the GitHub if I just go and search in the Bing over here you can see that this is this container d. iio and if I go and hit this you will see that container D is the industry standard container runtime with an emphasis on Simplicity robustness and portability so you can see that now this container D is graduated within the cncf or Cloud native Computing Foundation project and it has quite a lot of details over here and I will just recommend you to just go through how container D works and you can understand the overview and stuff in a nutshell container D is a very big project and it is now not only just used in Docker but also in kuber Nats and other major project for the containerization of the applications so that's what is the container D is all about and we have already discussed about it a bit but most importantly this container D also act as an intermediatory between the higher level orchest ation tools like Docker or kuber nates and to the lower level container runtime which is the runc so we have seen in the architecture that the container D talks to the runc so runc is also of the core component in the darker architecture and it is responsible for running the container process so this is one of the most important stuff as well and it is one of the lightweight and portable container runtime that will be used for spawning and running containers on Linux according to the OC I specification so this is another runtime that you need to understand and there are many different run times available not just about runy but you can keep on using many different run times if you think so just not to go too deep into the architecture you can see that this is what is happening behind the scene while you call from your command line that hey Docker just create an container from the image which is given then it is going to do all these operation for you and similarly if you're going to pull an image from the Hub do do.com then it is going to do all these operations so all these are happening for you behind the scene while you perform any action it's a simple command from the command line terminal so hope you got the idea of how the architecture of Docker works and this is what exactly makes Docker so interesting because this technology is now serving millions and millions of applications running on cloud

Channel: Execute Automation

Views: 395

Keywords: Udemy, course, executeautomation, testing, Windows, Docker hub, docker container, docker images, What is docker images, Downloading images, containers, what is containers, understanding containers, docker CLI, manage docker images, manage docker container, understand docker cli in seconds, docker works, Docker architecture

Id: C2PpkZjqDmc

Length: 5min 24sec (324 seconds)

Published: Thu Jul 04 2024