Docker Full Course 2026

[00:00] Ever wondered how tech giants like [00:01] Spotify and Netflix scale their software [00:04] so fast? The secret is containerization [00:07] with Docker as the essential tool at its [00:10] core. This structured hands-on Docker [00:13] course will take you from absolute [00:15] beginner to job ready, providing the [00:18] practical skills needed to build, test, [00:20] and deploy containerized applications [00:24] reliably. Isa from Dolphin Ed created [00:26] this course. [00:30] Have you ever wondered how tech giants [00:32] like Spotify, Amazon and Netflix, they [00:35] ship software faster and they scale [00:38] instantly? [00:39] The secret is containerization and [00:42] Docker at the heart of it. In today's IT [00:44] world, Docker is everywhere from [00:47] startups to tech giants and Inc. 500 [00:50] companies and it is the core tool or the [00:52] containerization is the core tool behind [00:55] cloud devops software development modern [00:59] security roles and modern application [01:00] architectures. Docker has become the [01:03] gold standard when it comes to shipping [01:05] and deploying applications that run [01:08] efficiently and reliably in the cloud or [01:10] on premises. The industry is shifting so [01:14] fast. Companies are containerizing all [01:17] the applications or the legacy [01:18] applications that they can and maybe [01:20] shifting that also to the cloud and [01:22] Docker has become a primary skill in [01:25] that revolution. Learning Docker now [01:27] means you are not just keeping up but [01:29] you are getting ahead and also learning [01:32] Docker now is going to pave the way for [01:34] you to learn Kubernetes the gold [01:36] standard when it comes to orchestration [01:38] and management of containers at scale. [01:42] Whether you are an IT fresher switching [01:44] into IT or an existing IT professional [01:47] upskilling, [01:49] this course is your complete structured [01:51] stepbystep practical guide to mastering [01:54] Docker. And the course will take you [01:56] from the absolute scratch to becoming [01:59] job ready using Docker in deploying [02:01] applications and services. The course [02:04] will start from the very basics from [02:06] comparing virtual machines to [02:08] containers. Why do we need containers [02:09] and how Docker transforms the way we [02:13] build and deploy applications? [02:15] Then we'll dive deeper into Docker by [02:18] learning what is a Docker file and how [02:20] we can create an image from a Docker [02:22] file and how we can deal with Docker Hub [02:25] and build repos where we can ship the [02:27] created images and then understanding [02:30] and working with Docker networking [02:32] storage and volumes and then deploying [02:35] multi-container applications using [02:37] Docker Compose and it doesn't stop there [02:40] but it will take you further to [02:41] introduce what Docker Swarm is which is [02:45] an Orchestration management for Docker [02:47] containerized applications by Docker. [02:50] The course is hands-on, practical, learn [02:53] by doing, basically creating Docker [02:55] files and images and containers and [02:57] applications and browsing to them and [02:59] Docker Compose and writing YAML files [03:01] and much more. By doing all of this with [03:04] quizzes and assignments in the [03:06] respective modules and real world [03:08] projects at the end, this is all what [03:10] you need to go from zero to hero in [03:13] Docker. By the end of this course, you [03:15] will walk away confident to build, test, [03:18] and deploy containerized applications [03:21] using Docker and Docker Compose and will [03:24] be ready to deploy these real world [03:26] skills in any IT role that requires [03:29] these skills. [03:35] My name is Isa Abu Sharif and I have [03:37] been in IT for more than 25 years now. I [03:40] am an AWS certified instructor and I am [03:42] a Cisco certified instructor since 2005. [03:46] I hold many IT certifications and [03:48] infrastructure certifications as well [03:50] including the Cisco certified internet [03:52] network expert. I have been teaching for [03:55] more than 21 years now as a certified [03:57] instructor and I have taught networking [04:00] and I have taught management and I have [04:02] taught uh infrastructure cloud and [04:05] automation and devops courses and in [04:08] addition to that I have also been in the [04:11] IT industry myself as an architect as a [04:14] consultant at IBM in the US and at Cisco [04:17] and other companies. So I have blended [04:20] all of that experience to explain to you [04:24] in layman terms very easily from the [04:26] ground up what containerization is, why [04:29] do we need it and how we can work with [04:31] it. So that at the end of the course you [04:34] will be able to work confidently with [04:37] docker and that would be the a stepping [04:40] stone for you to learn kubernetes which [04:43] is orchestration and management for [04:45] containerized applications at scale. So [04:48] you will not be bored and you will be [04:49] entertained throughout the course. It's [04:51] going to be engaging and not boring. I [04:53] promise. And at the end you will be [04:55] proud of the time you have invested in [04:57] this course. [05:02] This course would never be possible [05:04] without your support. In order to [05:07] support us develop more free content [05:09] that is high quality at no price to you [05:12] like this one, consider buying the full [05:16] package of this course on [05:18] www.dolphined.com. [05:20] It can be found at this address [05:22] www.dolphinet.com/courses/doccker. [05:26] Very easy URL to follow. And for a price [05:30] of a lunch or even less with the [05:32] inflation that we are living in right [05:34] now, you can support us develop more [05:36] free and quality content like this one [05:39] to help you throughout your learning [05:41] journey and to help the masses as well [05:43] across the globe. If you buy the full [05:45] VIP package, as I like to call it, [05:48] you're going to have lifetime access to [05:50] the content and its updates. It's going [05:52] to be split into video lectures. So you [05:54] don't have to be overwhelmed with seven [05:56] or eight hours or even 15 hours a single [05:58] video. You can have that divided into [06:02] separate lectures for theory and [06:03] hands-on. You are going to have access [06:06] to the full 15 hours version of this [06:08] course. And you're going also to have [06:10] additional hands-on labs on the topics [06:13] that we have covered. But at at a deeper [06:15] level, you'll have a second realworld [06:18] capstone project that will deepen your [06:20] real world experience with Docker. And [06:23] also you'll have a community access to [06:25] that community for faster Q&A support. [06:29] And of course, the ability on our [06:31] platform to have quizzes and assignments [06:33] is going to be there as well. And also [06:36] you'll have access to the scripts for [06:38] all the hands-on labs and the 330 pages [06:41] PDF guide that includes all the slides [06:44] of this course. We appreciate your [06:46] support if you can and that would [06:48] definitely be a good return on [06:50] investment to yourself as well through [06:53] more free content that we can generate [06:56] through your support. In this course, we [06:58] are going to cover the following topics. [07:01] We're going to introduce what Docker is [07:04] and why do we need containers and how [07:06] they are different from physical servers [07:08] and virtual machines. Then I'm going to [07:11] take you to set up Docker on a free [07:16] virtual machine, Linux virtual machine [07:18] on AWS. So I will teach you how to [07:20] create AWS account and whatever you are [07:23] going to do is going to be free. So you [07:25] don't have to bother about installing on [07:27] your laptop or creating virtual machines [07:29] on your laptop and at the same time you [07:30] will be practicing what you will do in [07:33] the real job if you like to practice [07:36] Docker with confidence. Then I'm going [07:38] to take you to what Docker is and the [07:41] architecture of Docker. Then we are [07:43] going to move on and start to learn [07:46] docker commands and how to use that to [07:48] create containers of different use cases [07:51] with different base images. Then I will [07:54] explain to you how we can create a [07:57] container from an image. I'll take you [07:59] to docker hub and explain to you that [08:01] there is a repository of free available [08:05] images that you can just download and [08:07] create containers from. And I will also [08:09] teach you what if you have an [08:10] application that doesn't have an image [08:12] and you would like to run it in [08:14] containers. So how you can containerize [08:16] that through docker files. From there [08:18] we're going to jump into docker [08:20] registries. So now in your corporate if [08:23] you are the master of docker and you are [08:25] creating containers for your company. [08:27] Now where do you store them? What's the [08:30] repo repository or the registry as we [08:33] call it in docker that you can upload [08:36] your images to? And it's up to you. You [08:38] can make them public so anybody can [08:40] benefit from them or you can make them [08:42] in a private registry where only the [08:44] corporate members that have access to [08:46] that repo will be able to login [08:48] authenticate and download that to create [08:51] containers from. Then we are going to [08:53] introduce the docker networking and how [08:56] can that be used how you can access the [08:58] containers from the outside and we are [09:00] going to look at docker compose and how [09:03] we can automate the process. Instead of [09:05] doing that manually, we are going to get [09:07] into how we can write YAML configuration [09:10] files for compose where you can do that [09:12] automatically through compose. Then we [09:14] are going to look at persisting data in [09:17] your containers. What if the container [09:19] dies? It's just a software process as we [09:21] learn. What if it dies? I lose all the [09:23] data. What if it was a database and it [09:24] has very critical data? What do I do? [09:27] Then how we can persist the data by [09:29] mounting volumes or bind mounts outside [09:32] the container. So if the container dies [09:34] I can create another one that attaches [09:36] to the same data or I can make the data [09:39] available to multiple containers at the [09:41] same time. From there we are going to [09:42] work on a project real world project [09:45] where you will you are going to deploy [09:46] what you have learned and you are going [09:48] to understand better how this works how [09:51] this containerization of application or [09:54] microservices happens and from there we [09:56] are going to wrap up and I assure you [09:58] that you will be confident at the end [10:00] and you are going to use docker with [10:03] comfort. So whether you are a fresher [10:06] into IT or someone changing career into [10:08] IT or you are already into IT but you [10:10] don't know Docker, you have to learn it [10:12] now. So without further ado, let's get [10:14] started. [10:21] Why do we need to learn Docker and why [10:23] Docker? Why is what is so special about [10:25] Docker that we need to learn it? [10:28] So, Stack Overflow in 2024 did a survey [10:32] and asking the contributor or those who [10:35] contributed to the survey what are the [10:38] most popular developer tools that they [10:41] are commonly using or they prefer to [10:43] use. And as you can see over here that [10:46] Docker was at the top with a 50 plus% [10:53] and this is number one like this was [10:55] voted the two number one by 53 point [10:57] something of the contributors or the [10:59] respondents the survey. Now if we think [11:03] what about if we send out a survey and [11:07] we get the feedback which are the top [11:09] three tools do you think the ones that [11:11] will include Docker as number one or two [11:13] or three are going to jump to maybe 70 [11:16] 80% and I truly believe it might be even [11:19] higher than that one might ask okay but [11:21] these are developers machine learning [11:24] ops engineer or maybe I'm an AI engineer [11:27] maybe I'm a data scientist or a data [11:28] analyst or maybe I'm a cloud engineer [11:31] you might I think this is not relevant [11:32] to me. We just picked developers. [11:34] Actually, Docker applies to all IT [11:36] professions nowadays from the simple [11:40] automation all the way to hosting [11:42] applications at a large scale. So [11:45] containers are in the heart of that. Of [11:47] course, Kubernetes when we are talking [11:49] about a very large scale deployment [11:51] would be the right thing to do, but [11:53] Docker and Docker based applications and [11:55] environments and clusters are very [11:57] common as well. if the scale is not that [12:00] large and the complexity required or [12:02] desired is not high as well. [12:06] So why do what is so special about it? [12:09] Why are developers loving it? And why do [12:11] everyone have to learn it? It has a lot [12:13] of features but among these the top four [12:17] are environment reproducibility. [12:20] So you can recreate what you do on your [12:23] laptop if you follow the same steps. You [12:26] can recreate it in production, in [12:27] development, in testing, in the cloud or [12:30] on your laptop or on premises. Same [12:34] result. If you follow the same [12:36] instructions and the same steps, you get [12:37] exactly the same result, which is [12:40] excellent and amazing because last thing [12:42] you want to do is developers work on an [12:45] environment. When you try to recreate [12:48] that environment, then you have [12:50] differences and then when you test, then [12:53] you get problems. But the developer will [12:56] tell you it works on my machine. That is [12:59] why Docker was invented. We don't want [13:01] to listen to it works on my machine then [13:03] it should be your problem. Then you take [13:05] it from testing into production and then [13:07] you have more issues. So reproducibility [13:10] in Docker is top-notch. [13:13] Second one is dependency management. you [13:16] have multiple things on the virtual [13:17] machine or the server, multiple [13:19] applications and some tool requires [13:23] Python version 2.7 whereas the [13:26] application that is built by Flask needs [13:29] Python 3.8 or 3.9 [13:32] then now we might start to get into [13:35] conflicts and dependency management is a [13:38] very important thing when we are [13:40] developing software and tools and [13:41] applications. So dependency management [13:44] is very easy in Docker and we're going [13:46] to explain why. Portability is very easy [13:49] when you are dealing with containers and [13:51] with Docker as an example and that is [13:54] very important because today I'm on AWS [13:56] tomorrow I'm going to be on premises or [13:57] maybe I'm going to move to Azure or [13:59] maybe I need to replicate my environment [14:01] in Google cloud then in that case [14:04] portability is very key and hopefully [14:07] the size of the data that has to do with [14:09] my application is not very large. So I [14:12] can just transfer it maybe in 10 15 [14:14] minutes and start working on it or maybe [14:16] I ship it somewhere on the cloud and [14:18] pull it from the other side. So [14:20] portability is key and this is very very [14:22] important when it comes to working with [14:25] applications and modern applications to [14:27] be more specific. [14:30] Last but not least on the top four [14:33] reasons why Docker is very popular is [14:36] the fact that when you deal with Docker [14:39] configurations are scripted in text [14:42] files. So it's very easy to track them. [14:45] It's very easy to have them on GitHub [14:47] and then you can track the different [14:48] versions and what changed between every [14:51] minor version to the next or maybe every [14:54] minor to a major release and why were [14:57] the changes done. uh we added this [14:59] database we updated to um engine X [15:02] version X and Y and Z we did Ubuntu [15:06] version 20.04 04. [15:10] So you can track the changes and it's [15:12] very easy to roll back if needed or to [15:14] go back in history and find out. Okay, [15:16] so why do we have an issue now and we [15:18] didn't have that before. So version [15:19] control is very key. So these are the [15:22] four top reasons why you need to learn [15:23] Docker and you need to do it right now. [15:30] where the technology started and we'll [15:33] go back into the physical servers era [15:36] and then we'll take it through [15:37] virtualization. Why are we doing this? [15:40] Because if you are a newcomer into IT or [15:42] shifting into IT or you haven't dealt [15:45] with servers and virtual machines and [15:47] all that before it makes a lot of sense [15:50] to give you a brief of what used to [15:52] happen and why did we get into [15:55] containers. So this is going to be your [15:58] introduction into that. If you are a [16:00] well seasoned professional and know what [16:02] virtual machines are and what physical [16:05] servers and data centers and all that [16:07] then you can skip this section and move [16:08] to the next one. [16:12] So let's start by finding out what is [16:16] common between the different computing [16:19] devices. And when we talk about [16:20] computing device, could be a server, [16:22] could be your laptop, could be an iPad, [16:24] could be your phone, it could be any [16:27] digital device that is functioning at [16:29] your home or in the office or maybe in [16:32] the malls and so on. Any comput device [16:35] components will have a number of [16:38] components. Any computing [16:41] any computing device will have a number [16:43] of components, but the most common ones [16:45] are it will have a CPU. It will have the [16:49] engine that can process everything that [16:52] comes to it, instructions, programs, [16:54] applications, Microsoft Word, Excel and [16:56] so on. [16:58] So the CPU is the central processing [17:00] unit or you can say that it is the one [17:03] that does the work. [17:06] Then we have random access memory and [17:09] that's called the RAM. We have it in [17:11] your laptops when you when we tell you [17:13] that your laptop has eight or 16 or 32 [17:16] gigs of RAM. So random access memory is [17:19] where the applications are open are [17:21] executed while you are using them. So if [17:24] you are running let's say Facebook for [17:26] example or Instagram actually that is a [17:29] program that will be executed when you [17:31] open it in your devices random access [17:34] memory and as long as you are using it [17:36] before you shut it down or close it it's [17:38] going to be in the RAM. [17:41] Then we have the hard disk drives. This [17:43] is where the storage is. When you switch [17:46] off your phone and then you start it [17:47] again, the images, the photos, the [17:50] videos, and the contacts are still [17:52] there. How come they were not in the [17:54] RAM? When they are executed, they are in [17:56] the RAM, but when they are in storage, [17:59] when you shut it down, it's going to be [18:01] in the hard drive. And that could be [18:03] multiple types, SSDs or HDDs. [18:06] And then we have how can we communicate [18:08] to the outside world? Even if it is your [18:10] phone, how are you getting on the [18:12] internet from your phone? There has to [18:13] be some transmission and reception [18:15] device on your phone. So when we talk [18:18] about servers and all that, we have what [18:19] we call the neck cards or the network [18:21] interface cards. And they could be Wi-Fi [18:23] ones or they could be wired. A cable [18:25] connects from here. So this is going to [18:27] be inside your device, inside your [18:28] server or laptop or computer or desktop. [18:31] And then a cable will connect it to the [18:33] network and that's how it communicates [18:35] with the outside. or it could be [18:37] wireless where it's just connected to a [18:39] Wi-Fi network and so on. [18:42] Then we have what we call GP GCPUs or [18:45] graphics central processing units or [18:48] GPUs and these are the ones that will do [18:51] the heavy work when it comes to [18:52] rendering videos or processing enhancing [18:56] the processing time and so on. So think [18:58] of them as additional CPUs that can do [19:01] specialized functions and that will [19:03] speed up what you do on your computer. [19:05] So any computing device will have these [19:08] components among other ones battery and [19:10] plugs and all that. We are not but we [19:12] are not interested in these for our [19:14] discussion. [19:16] All right. So I have a laptop and you [19:18] have a desktop and you have an iPad. But [19:20] what is a server? Why do we talk about [19:22] servers when we talk about applications [19:25] and the internet and the cloud and so [19:27] on? Because your laptop despite it could [19:30] be 2025 model but it's not powerful [19:33] enough to serve a thousand or 10,000 or [19:36] 100,000 users that would like to get [19:38] into your e-commerce website and buy [19:41] stuff from you. So hosting your [19:43] e-commerce website on your laptop will [19:45] not scale. And that's why we talk about [19:47] servers and this is where we put the [19:49] applications. Of course it could be rack [19:52] mountable like the one that you see on [19:53] the screen right now but they could be [19:56] desktop servers as well. So with a box [19:58] like a desktop computer, but the main [20:00] difference between a laptop and a server [20:03] is how powerful the server is, the [20:05] muscles, how many CPUs, how many how [20:08] much memory it has and so on. [20:11] So server components are like any [20:13] computing device. So it has as we [20:16] mentioned it has a CPU, has a memory, it [20:18] has a disk drive, whether it is HDD or [20:21] SSD. It has [20:24] network card or network cards and has [20:26] GCPUs, but it's much more powerful. It [20:29] has a lot of these quantities. It could [20:31] have 16 tab of RAM, 64 tab of RAM, way [20:36] more than what your laptop would have. [20:39] The number of G CPUs, the number of [20:41] GPUs, the number of disk drives, the [20:43] number of network interfaces. So, you [20:44] can think of it as a big muscle compute [20:48] device. Basically, that's what the [20:50] server is. And this is where Amazon.com [20:52] and CNN.com and eBay and all the big [20:55] top-notch and the big companies are [20:57] hosting their applications and services. [21:02] And of course, as your laptop, which is [21:04] maybe a Mac or maybe it's a Windows one [21:07] or a Linux one, it will have an [21:09] operating system. The operating system [21:11] is the one that uses the hardware, the [21:14] RAM and the disk and the memory and so [21:16] on. So that's the orchestrator on how [21:18] these work. And that will be the [21:21] mediator between your applications and [21:23] tools and the hardware. So this is the [21:26] translator or the brain at the end is [21:28] the software. [21:31] And of course it it depends on how you [21:34] want to do it. You can have multiple [21:37] applications on your server. So we have [21:40] the operating system on top of which we [21:42] can install tools and applications and [21:44] so on. [21:47] All right. So okay fine. I'm going to [21:49] buy a server. I'm going to have that. [21:50] But as the number of users increases, [21:53] maybe that server is going to be really [21:55] exhausted, overwhelmed to a point where [21:58] it may slow down or just break apart. It [22:01] cannot serve 1 million users who are [22:04] trying to come because it has so much [22:06] memory, but it has been exhausted. It [22:08] has so much CPUs, but the users have [22:10] been using them and the operating system [22:13] is unable to handle that 2 million [22:16] requests per minute that are coming in. [22:18] So in that case we need to add more [22:21] servers and that is called scaling [22:23] servers. So in that case add two more, [22:26] four more, five more, six more of course [22:29] there is a process and a logic behind [22:31] how many you would increase and that is [22:34] physical servers but when it comes to [22:36] the cloud they're going to be logical [22:38] and autoscaling configuration. [22:41] As the number of servers increases we [22:44] cannot keep them under my desk in my [22:46] office. I have to move them into a [22:47] secure place. And this is where the talk [22:50] about data centers started about 20 [22:53] years ago. They used to call them server [22:54] farms before. So data centers are [22:57] massive locations, real estate location [22:59] that is airond conditioned, secured, [23:01] monitored and prepared. And as you can [23:04] see in the picture, it has cabinets [23:06] where this is one server for example in [23:09] that. So this is a second server and so [23:12] on. So each one of these is a server and [23:14] then from the backside they're going to [23:16] be cabled and connected to the network [23:18] and this could be part of Facebook or [23:21] Instagram or Google or one of the data [23:24] centers one of the big data centers okay [23:26] when the cloud started data centers are [23:28] now becoming hosted by providers like [23:31] AWS like Azure like GCP like Alibaba and [23:35] so on but in essence a data center is a [23:38] data center so number of racks there [23:40] could be thousand of racks [23:42] And they are built in rows in a very [23:44] clean place that is air conditioned, [23:46] monitored, powered, secured with [23:49] surveillance with access control and so [23:51] on to host the applications on servers. [23:57] All right, so we have the server. We [23:58] bought the most powerful one and we [24:00] spent $200,000 on that P server platform [24:05] and life is good. Now it can handle 2 [24:08] million requests and then we needed more [24:10] because our business is growing and we [24:11] added more servers and so on. Now when [24:15] you have one server and you start [24:17] installing different applications let's [24:19] say 3 4 5 10 20 we are just dumping [24:23] applications on the servers and then we [24:25] realized we started to have issues. Why? [24:29] Because I have multiple applications [24:31] written in Python but they need [24:33] different versions of Python. Some of [24:34] them are old, some of them are new and [24:36] now they need different runtimes or [24:39] maybe Java and they need different [24:40] versions and runtimes. Similarly, we are [24:43] running MySQL version 8 and MySQL [24:46] version 5 and all dumped on the same [24:48] server. Now, someone comes to [24:51] troubleshoot a problem for application A [24:54] and then looks at it say Python 3.8. No, [24:58] that's wrong. Delete the file. Let's [25:00] download Python 2.7 and that's the right [25:03] one. Then that breaks another [25:06] application that was using that file. So [25:08] dependencies and versions and all that [25:11] is an issue when you start dumping [25:13] applications on the same server. One [25:15] would say, okay, so why do we have more [25:18] than one application? Why don't we have [25:19] one application per server? Yep, that's [25:21] easy. But the server is very costly and [25:24] you would like to use or to utilize the [25:27] resources within the server as much as [25:29] you can. But doing so and putting more [25:32] applications ended up being dependency [25:35] issues and troubleshooting and errors [25:38] and all that. So drawbacks include [25:40] resource contention and inefficiency, [25:43] dependency conflicts for different [25:44] versions, lack of strong isolations, [25:48] the admin of one application can see the [25:53] files for the other application and he [25:54] has or she has no clue about what that [25:57] is and they start deleting and changing [25:59] things. So you have security risks. If [26:01] one application is compromised, [26:02] everything else on the server is also [26:04] compromised because of the lack of [26:06] isolation and I want to scale app one [26:10] because it's in high demand and all [26:12] that. But app two and app three are [26:13] okay. So what do we do? We add more [26:16] servers and we only dedicate them to app [26:18] one. How about the resource utilization [26:21] on the additional servers? Because app [26:22] two and app three, they don't need that. [26:24] They have enough power on that one or [26:27] two servers. So adding more that means [26:29] it's going to be waste of money because [26:32] the resources are going to be very well [26:34] utilized and of course deployment and [26:36] maintenance hell and add to that what if [26:38] you want to move it to another data [26:41] center I want to move that application [26:43] we are now growing so we bought a new [26:45] facility a new headquarter and we would [26:48] like to move our stuff so now we need to [26:50] move the physical servers not just take [26:52] a backup and then move the backup on the [26:54] other side so it becomes a painful thing [26:57] with physical servers and that's why [26:59] they said okay why don't we just go into [27:02] virtualization which is the next step [27:04] and of course lack of portability as I [27:06] mentioned [27:08] so that had led to a solution called [27:11] virtualization why don't you split your [27:15] physical server the one that has the [27:17] biggest muscles on earth and split that [27:20] into multiple virtual servers and you [27:24] have this much disk space and you have [27:27] this much RAM and you have this much [27:28] CPU, why don't you virtually split that [27:31] among the virtual servers and that will [27:34] give you the isolation you were looking [27:35] for. That will give you the best [27:38] utilization for your server resources [27:40] and that will also give you the [27:41] portability if there is a way I can take [27:44] a backup of each one of these virtual [27:46] servers which is going to be much less [27:48] than a physical server and then move it [27:50] into the other location and scalability. [27:53] Now put app one into a virtual machine, [27:55] put app two in a different virtual [27:56] machine and so on. So this is how it [27:58] looks like. So in virtualization [28:01] so as you can see here and here they are [28:04] identical operating system they could be [28:06] identical both are Windows or Mac or [28:09] Linux but then we introduce an emulation [28:14] layer on top of which we start creating [28:17] what we call virtual machines. So we [28:19] start to create the virtual machines or [28:21] the virtual servers and we put app one [28:24] in one server, app two in another, app [28:26] three in another, database my SQL in a [28:29] fourth one, database reddis in a fifth [28:31] one and so on. [28:34] So we did that. So the hypervisor would [28:36] make each virtual machine feel that it [28:40] has all the required disk, memory, GPU, [28:43] CPU, network cards and so on that it [28:46] needs for the operating system to [28:48] function and for the applications to [28:50] function. So this could be a virtual [28:53] machine with a Linux let's say real Red [28:55] Hat Enterprise Linux. This could be a [28:57] Windows [28:59] server and this could be a Linux Ubuntu [29:01] based for example. So now we can have [29:04] different operating systems. They are [29:07] isolated from one another and I can deal [29:10] with each one of them as a one app [29:12] virtual machine. So now isolation and [29:14] conflicts and dependencies and all that [29:16] disappear and I have better portability. [29:19] So this introduced us to the concept of [29:21] virtualization which has been ongoing [29:24] since 2003 2004 time. [29:29] So virtualization allows us to run more [29:32] than one virtual machine, multiple [29:34] operating systems and application on a [29:36] single physical server which is a good [29:38] thing. They are isolated and we can take [29:41] a backup of each virtual machine. But of [29:43] course the backup is going to be a good [29:44] size because it does have a full [29:47] operating system. So full operating [29:49] system plus the apps and so on. This is [29:52] going to be in the tens of gigabytes in [29:54] size. And a VM is going to be a set of [29:56] files obviously. [29:59] So what are the resources that the [30:02] hypervisor facilitated access to for [30:04] each virtual machine. [30:07] So it will grant it or provide it with a [30:10] vCPU, v memory, vesk and v network card, [30:15] vgcpu and so on. So why do we say v? [30:19] Because this is a virtual machine and [30:20] this is not a physical. This is an [30:23] allocation of the actual CPUs on the [30:26] physical server. So that's why we call [30:28] it vCPUs, vmemory or vramm and vesk and [30:32] v neck and and so on. So each virtual [30:35] machine will be given what it needs for [30:38] its operating system. We call it the [30:40] guest OS and the applications to be [30:43] installed successfully and to perform [30:45] successfully on the virtual machine. [30:48] That's why we have the V-neck, we have [30:50] the vesk, and we have the vramm and the [30:52] vcpu for each virtual machine. [30:58] What are popular hypervisor providers? [31:01] We have VMware vSphere, we have Zen, we [31:04] have Microsoft HyperV, and we have Linux [31:06] KVM, we have Oracle VM Virtual Box, and [31:10] we have VMware Workstation. [31:13] Virtual machines despite they are much [31:15] better than physical servers for the [31:17] reasons we have mentioned but they have [31:19] issues as well. So first one is they are [31:22] heavyweight. Each one of them has a full [31:24] operating system and the applications [31:26] and so on. So they are slow to start. [31:28] They could take minutes to start [31:30] depending on how many apps and packages [31:32] are installed. So limited scalability [31:35] because the physical server has so much [31:38] memory and so much discs and all that. [31:39] So it I can go maybe to 5 10 15 60 [31:44] virtual machines but then what I have to [31:46] spin another physical server and so on [31:49] and the problem with the reproducibility [31:54] is an issue. So a developer is working [31:56] on the app works perfect on his machine [31:59] or virtual machine on the server but now [32:02] ships the image to the testing team but [32:05] the testing team when they are starting [32:07] the application there is a lot of errors [32:09] but then he would say oh but it works on [32:11] my machine it's your problem there is [32:13] something missing maybe dependencies [32:15] maybe you have the wrong versions you [32:17] need to make sure that everything is [32:19] exactly like the long list I have boom [32:22] go ahead and build the same machine or [32:25] you know what come and take my physical [32:27] server ship it to your location and work [32:29] on it. Of course that's stupid to do. [32:32] So the repro reducibility will be a [32:34] problem with virtual machines and we [32:37] have multiple operating system. Each [32:38] virtual machine requires its own [32:40] operating system. So let's say I have [32:43] three virtual machines and they're all [32:46] Windows but then I have I need the [32:47] license for the first one, the second [32:49] one and the third one. I need to install [32:50] a complete Windows on each one of them. [32:52] I need to start that. that I need to [32:54] take the resources and the disk space [32:56] and the memory for each one of them. So [32:58] that's a waste of resources or [33:00] inefficient use of resources. [33:03] Image management, the virtual machine [33:05] image management is not as easy [33:07] especially because of the size and [33:09] because of the lack of reproducibility [33:12] perfection that we talked about and [33:15] portability of course is going to be an [33:16] issue based on what we have discussed. [33:24] So what was the reason or what were the [33:28] drivers of looking into containers if we [33:30] had virtual machines. So this section is [33:33] going to take us from the virtualization [33:36] to containers and what was the [33:38] background what was the reason that we [33:40] moved or technology moved into [33:42] containers. We still have virtual [33:44] machines but the more popular are the [33:47] one that is getting more attraction is [33:51] the containerized the cloud native and [33:54] the containerization docker kubernetes [33:56] and all that. [33:59] So before we delve into this let's find [34:02] out or let's understand what is a Linux [34:05] software process or what's a software [34:07] process in general if we are talking [34:09] about Linux or Microsoft Windows and so [34:11] on. So the process in Linux terms is a [34:15] running instance. So an execution of a [34:19] program. [34:20] So let's say for example engine X or um [34:23] Tnet or Ping or anything any program. So [34:28] any tool or any program that when it is [34:30] executed [34:32] it has its own memory. It has its own [34:35] CPU resources and system resources but [34:38] it is managed by the operating system [34:40] kernel or the Linux kernel. [34:43] So if I have Apache for example or [34:46] engine X or Tomcat or whatever is the [34:49] program that I'm running or maybe a [34:50] calculator on Linux or Python and then I [34:54] run it then it's going to be run as a [34:56] separate process kind of isolated from [34:59] what is around it. So when we run any [35:03] program in Linux like bash, engine x, [35:05] python, apache and all that. So what [35:07] would the Linux kernel do? It will load [35:09] the program code into memory. We're [35:12] talking about RAM, the random access [35:13] memory. It will allocate it a unique [35:16] process ID or P P ID and it will create [35:20] a process to execute the code. So these [35:22] are the three things that will happen [35:24] each time we run a program. So each time [35:27] you run a program or a tool that you [35:29] have in Linux, there will be a process [35:31] generated based on that. [35:34] Why did we mention that? Because [35:36] containers when they run into [35:40] Linux or or Windows, they run as [35:43] lightweight isolated process that is in [35:46] a shared operating system. As we will [35:48] see throughout the lab that we're going [35:50] to run all of that on Ubuntu Linux. So [35:52] each time when you run a container, it's [35:54] going to be a small size, lightweight, [35:55] like a small size. It doesn't need a [35:58] full operating system. We're going to [35:59] get into that. And everything that [36:02] container, let's say the container is [36:04] for Apache or EngineX, anything that it [36:07] needs in order to run in terms of code, [36:11] libraries, environment variables, [36:13] runtime, configuration files, they are [36:15] all going to be within that process. [36:19] So let's take a simple example. Python [36:21] calculator written in Python. In order [36:24] for Python to run, it needs to have the [36:28] runtime. So basically the interpreter [36:30] that will take the Python commands and [36:33] tell the machine or tell the hardware [36:35] and software what to do with it. [36:37] So that with any tools or configuration [36:41] files and with the code in Python itself [36:44] and with any environment variables, [36:46] usernames, passwords and so on, all will [36:49] be encapsulated into what we call the [36:51] lightweight isolated process which is [36:53] the container. And this is why we [36:57] brought into attention the Linux process [37:00] or what is the Linux process? If you put [37:03] that in a visual format, let's say that [37:05] the container is this box [37:08] um we we are just trying to visualize [37:10] it. This is not we don't have boxes in [37:12] operating systems. So the code in Python [37:16] in my example, the runtime, the [37:19] interpreter, the Python 3 that will run [37:21] this and any configuration files [37:24] required and any binaries or [37:27] dependencies or libraries that are [37:28] required. For example, if I'm running [37:31] deep math, there is a lot of libraries I [37:33] can load in Python that would help me [37:35] with that. If I'm doing data analysis, [37:37] machine learning, AI, data science, [37:40] analytics, then there will be a lot of [37:41] libraries I can load that will help me. [37:43] All of that is going all together be put [37:46] into the container and the container [37:48] will be considered the program that when [37:50] I run it will run in an isolated [37:52] process. [37:54] Think of shipping containers. So let's [37:58] say the container on the top. If I [38:00] shipped that container and I put all my [38:02] furniture and my appliances and all that [38:04] inside the container and it is closed. [38:06] Now if I decide to send it to Latin [38:08] America when I go there I'm going to [38:10] find exactly the same. If I decide to [38:14] move to Australia the same container [38:16] then it will be shipped to Australia. [38:18] When I travel to Australia I'll find [38:19] exactly the same content inside that [38:21] container. So that's exactly the concept [38:25] of containers and it was derived or it [38:28] was inspired by the shipping containers [38:32] and of course we can run applications [38:34] inside containers because the code we [38:36] are talking about here will be more or [38:38] less to do a specific program a specific [38:41] function or to solve a problem or maybe [38:44] be part of an application. [38:47] the features of containers and the [38:49] reason why we're getting into that [38:50] because we are going to take a step back [38:52] afterwards and contrast that to the [38:54] issues or limitations we discussed with [38:56] virtual machines. So the features in [38:59] containers that they don't need a full [39:01] operating system and we're going to [39:03] explain how [39:05] each one runs into a process that is [39:07] isolated self-contained and it has [39:10] everything that it needs. [39:12] It is much faster because it doesn't [39:14] have a full OS and it is lightweight. [39:16] It's much faster to create, start, and [39:19] tear down. It's repeatable. The same [39:22] one, reproducible. Basically, the same [39:24] container if you run it here or if you [39:27] run it in Hawaii or if you run it on AWS [39:30] or on premises, it's going to be the [39:32] same thing, reproducible and definitely [39:34] like shipping containers in shipping [39:37] industry. It is portable and it's easily [39:41] scalable, lightweight software process, [39:43] then we can scale very easily. [39:46] All right. So that's all great, but how [39:50] can a container run without an operating [39:52] system? That's what I mentioned. And [39:54] there has to be a way to do it, right? [39:56] In order to build, ship, and run [39:59] containers, there has to be some magic [40:02] that happens on the host. If it is a [40:04] program software process, it has to be [40:06] running on a computing device, on a [40:08] server. [40:09] So how can that happen? How can we run [40:11] containers? Let's say this is container [40:13] one and container two. How can we run [40:15] this on this server that has an [40:18] operating system? There has to be [40:21] something that would allow the container [40:23] to feel that it has an operating system. [40:27] So it will lean on the operating system [40:29] of the host. So basically they are going [40:31] to share the kernel of the operating [40:34] system be it Linux or Windows or Mac OS [40:36] we don't care that operating system is [40:39] going to serve all the containers. The [40:41] kernel is going to serve all the [40:43] containers that are in the same host [40:46] and that emulation or that mediator is [40:48] called the containerization engine or [40:51] the container engine or if it is docker [40:53] then it's the docker engine. [40:56] So now we have the dotted line that [40:58] represents a container. It has the [41:00] application code configuration [41:02] dependencies binaries libraries anything [41:04] that it needs to run and it is a [41:06] self-contained entity that will run as [41:08] an isolated process. So without the [41:12] container engine we cannot run [41:14] containers and notice that we don't have [41:16] a hypervisor here. We don't need the [41:18] hypervisor. [41:19] So now we are sharing or we are allowing [41:23] the operating system to be served by the [41:26] engine the container engine to serve all [41:28] the containers and this is how the [41:31] containers don't need their own [41:32] operating system. [41:35] Containerized applications as we [41:37] mentioned they run into separate [41:38] processes isolated and docker is the [41:41] most popular container engine and it has [41:43] been out for about I don't know 12 14 [41:46] years now. Docker is available as a [41:49] community edition which is free and it's [41:52] also available as a paid edition which [41:54] is enterprise edition or e. All right. [41:58] So docker containers from the docker [42:00] file to an application. How can we start [42:01] a container? We looked at the previous [42:04] slide that there was an existing [42:06] container but where does it come from? [42:08] How do I start it? How do I write or [42:10] what do I need to do in order to [42:13] configure a container and allow the [42:15] operating system to find out that there [42:16] is a container. So we start from what we [42:19] call a docker file a script text that [42:22] you write down. Of course it has syntax [42:24] and there is some understanding and [42:26] knowledge behind it. Once you have that [42:29] docker file, then it will be used to [42:31] create what we call a container image [42:33] and the container image can be used to [42:36] run containers across different [42:38] environments. If you look at how this [42:40] happens, we have the docker file and [42:42] here's an example. It's a text file. [42:44] Remember when we said one of the [42:45] advantages of containerization is the [42:47] fact you can do version control. At that [42:50] time I mentioned that version control is [42:52] possible because it is more or less text [42:56] files. [42:57] So from the docker file we need to [43:00] create or build what we call an image. [43:04] And as we will see shortly that there is [43:06] a command called docker build. It can [43:08] take up a docker file and build the [43:10] image. So what's the image? That's the [43:14] template from which you can create [43:15] containers. Think about it like the [43:18] virtual machine ISO file for example [43:21] that from which you can build virtual [43:23] machines. [43:25] Now we can do a docker run command and [43:28] then we end up with the running [43:29] applications inside containers. And of [43:31] course this is reusable. So the image [43:34] can be used hundreds, thousands, tens of [43:38] thousands, millions of times without any [43:40] issues. [43:43] Let's put them side by side and do a [43:45] contrast. Virtual machines and [43:48] containers. [43:50] So on this side the hardware is exactly [43:52] the same. The operate operating system [43:54] could be the same. And then we have here [43:56] the hypervisor. The purpose of the [43:58] hypervisors was to emulate or let each [44:01] each virtual machine. Let's say this is [44:03] VM2 and this was VM1. So let's every [44:07] virtual machine think that it has the [44:09] right hardware that it needs. They were [44:12] not leaning on the operating system [44:13] because each one of them had its own [44:16] operating system full operating system [44:18] be it Windows, Mac or Linux or whatever. [44:22] On this side we don't have the [44:24] hypervisor the hypervisor but we have [44:26] the container engine docker engine and [44:29] then we have the containers running on [44:31] top sharing the kernel or the operating [44:34] system. So the way they share the kernel [44:38] is through the docker engine. [44:42] Now a question [44:44] can we run containers [44:47] on virtual machines? So here it's [44:50] obvious that we can run it on physical [44:52] servers. This is a physical server. [44:54] There is no hypervisor. So that is [44:56] absolutely a physical server. Now can I [44:59] run it on a virtual machine? And the [45:00] answer is absolutely you can. [45:03] And if we put both together in one [45:07] drawing it will be exactly like what we [45:09] see now. So we have the hardware the [45:12] operating system. This is the physical [45:14] server and then I have the hypervisor [45:16] which can create VM1 [45:19] and VM2 [45:23] in one of the virtual machines which has [45:25] a full operating system. I'm going to [45:27] install Docker engine a container engine [45:31] and the container engine will allow [45:33] containers to share the guest OS in this [45:36] type. So they don't have anything to do [45:37] with the external operating system on [45:39] the physical server. And on top of that, [45:43] as long as I have the Docker engine and [45:45] I have the operating system, then I can [45:48] run containers. That will be container [45:50] one. Here I'm talking about the internal [45:52] one and container 2 like the arrows [45:55] show. So I have virtual machines. I can [45:58] pick one of the virtual machines and [45:59] make it a container host [46:02] by installing the Docker engine or the [46:04] container engine and then they can start [46:07] working together. [46:12] sideby-side the comparison or why the [46:15] containers. How did we get the [46:16] containers from virtual machines? [46:17] Because we had the fact or the issue or [46:20] the limitation that virtual machines are [46:22] heavyweight, slow to start and that's [46:24] why containers are lightweight and they [46:26] start in milliseconds. [46:29] Virtual machines have limited [46:31] scalability because of the physical [46:33] hosts limitations. Containers they have [46:37] much faster scaling and they don't take [46:39] much time and they don't take much space [46:41] as well or resources. Virtual machines [46:44] are low in portability because of the [46:46] reproducibility limitations whereas [46:49] containers are have excellent [46:52] portability. [46:54] Virtual machines I have one operating [46:56] system in each one of them. So that's [46:58] more resources consumed by the [47:00] requirements of the operating system. [47:02] Whereas in containers they share the [47:05] operating system of the host. Here we [47:07] have inefficient image management. Part [47:10] of it is the size and the variations [47:12] between the different environments. [47:14] Whereas here it's efficient image [47:16] management and we will find out later [47:18] about docker hub and repositories where [47:21] or registries where you can ship your [47:23] built images and then they can be pulled [47:26] for whatever reason in whichever [47:28] location. [47:31] This one has poor development tested [47:33] production. Basically environment parity [47:36] will be poor. Whereas in containers [47:38] since they have everything within they [47:41] are excellent for different environments [47:43] and for CI/CD applications as well. [47:47] So what are examples of the popular [47:49] container engines and runtimes? We have [47:51] Docker, of course, that is going to be [47:53] the course. And then we have Linux [47:55] containers, and these are more low-level [47:57] containers that was before uh Docker, [47:59] the LX, LXC or Linux containers. And [48:02] there are system level containerization [48:05] framework. Then we have containerd which [48:08] is geared more towards Kubernetes. [48:11] And then we have Creo, which also is [48:14] geared towards Kubernetes deployments. [48:22] Let's talk about Docker architecture. [48:25] What are the components that make up [48:28] what we call a Docker host at the end? [48:30] What are the different software [48:32] components that play within the [48:35] container engine or docker engine in [48:37] order to allow us to perform or to use [48:39] Docker and create containers and tear [48:41] them down and so on. So, Docker is a [48:44] software platform. The Docker engine [48:47] that we discussed is a software. It's [48:50] not a hardware thing that simplifies [48:53] creating or building, running, tearing [48:57] down and while it is running managing [48:59] the containers or applications in [49:02] containers at a scale. [49:05] It is developed by Docker Incorporation [49:07] and it's an opensource software and it [49:11] virtualizes as we mentioned or allows [49:13] the sharing of the kernel the host [49:16] operating system [49:18] and the applications running in [49:19] containers they will be running in [49:21] isolated environments the processes that [49:23] we discussed and Docker can be a [49:27] community edition which is free anyone [49:29] can play with and there is an enterprise [49:31] edition that has additional features But [49:34] you have to pay for that. [49:37] So what are the components within a [49:40] docker host that in order to be able to [49:42] use it efficiently? Number one is the [49:44] docker client. That's the interface. [49:49] When you type anything any command that [49:51] starts with the keyword docker, then [49:53] that client is going to understand what [49:56] you want and that is going to send in [49:59] the request to the next component. So it [50:03] enables developers, users to interact [50:05] with Docker. That's the interface that [50:07] you have. And we can run commands like [50:09] docker pull, docker run, docker build. [50:11] Don't worry about that. We're going to [50:12] find about it later on. And we use [50:15] command line interface to do this. So [50:18] when we use the docker commands, what [50:20] happens is the client is going to [50:22] understand what you want. It will [50:24] validate it and then it will send it to [50:26] what we call the docker service or the [50:28] docker demon or dockerd. We're going to [50:30] talk about this next. [50:33] The next component is the Docker host. [50:35] That client, where does it exist? I need [50:37] a host. I need either a virtual machine [50:40] or a server in order to install the [50:42] Docker engine. And then I will have the [50:44] CLI. So that thing is called the host. [50:48] The virtual machine or the server where [50:50] the Docker engine is installed is called [50:52] the host. And as we mentioned, it can be [50:55] a physical machine, physical server or a [50:57] virtual machine. [51:00] Then we have the docker demon or the [51:02] name is dockerd which is the heart of [51:05] docker. That's the brain of docker. [51:10] Then we have docker images. So we start [51:13] with a docker file. We create the images [51:16] and then we create the containers. So [51:19] the images or the templates these are [51:22] read only binary templates and we can [51:24] use them to build containers and they [51:26] are reusable. I can build 1 million [51:28] containers from the same image and it's [51:30] not going to vanish or expire or be [51:33] depleted or anything. [51:35] So the templates they define the [51:38] application code where to get it or [51:40] download it from any libraries required [51:42] any dependencies any configuration files [51:45] any environment variables they are all [51:47] going to be in the image and obviously [51:50] they must have been in the docker file [51:53] which was transformed into an image and [51:55] now we can run the application that this [51:59] code is building inside containers. [52:03] So inside the host we have the demon and [52:05] then we have images. So we I can have [52:08] multiple images on my host. [52:11] Okay, let's zoom into the docker demon [52:13] to find out that heart of docker. What [52:16] exactly does it do? So the docker demon [52:19] is going to wait for API requests coming [52:22] from the client. We mentioned that the [52:24] client as you type commands it will [52:26] validate and then it will send in [52:28] requests to the demon and then it will [52:31] create containers and it will manage [52:33] them. It will create images, networks [52:36] and volumes. Okay. So the demon is going [52:40] to be the heart of all this. Is it [52:42] itself going to create that? Hold on. [52:45] We're going to come to which component [52:47] exact exactly within docker that is [52:49] going to do the actual creation and [52:51] management of containers. Also the [52:53] docker demon will build container images [52:55] as requested by the client. When you do [52:57] the docker build command, it's going to [52:59] build images from the docker files you [53:00] are pointing to. And it interfaces with [53:04] the docker registries. So it is the [53:06] middleman between the client the [53:10] registries and what happens on the host. [53:14] So when it interfaces with the [53:15] registries, it's either to publish, we [53:17] have created an image, let's put it on [53:19] the registry so people can benefit from [53:21] that or to pull an image that doesn't [53:24] exist but I need it. [53:26] So as requested by the client, the [53:28] docker demon will be able to do all of [53:30] this and it will manage the life cycle [53:33] of the containers from starting, [53:34] stopping, deletion or removal. All of [53:37] that is also managed by the demon. [53:40] So if we have the image and we have the [53:43] demon which are inside the docker host [53:46] then we can start building containers. [53:49] So containers are nothing more than [53:51] encapsulated environment which you can [53:53] use to run applications. [53:56] A container runs as a process in an [53:58] isolated environment. We know this it [54:01] packages the container packages the [54:03] application and its dependencies in a [54:05] single executable unit. the program or [54:07] the process that runs at the end. All [54:10] right. So since we talked about the [54:11] demon and the client and the host and we [54:14] talked about the images and the [54:16] containers then we need to also [54:18] highlight the registries where we can [54:21] host and store docker images. So if I [54:24] have an image then I can if I create the [54:28] image then I can ship it into the [54:30] registry. So it will be safe. If my [54:33] laptop crashes then it is in a safe [54:35] place. I can provide the link or the URL [54:38] for others to download that image and [54:40] use it and it I can make it public. If [54:42] it is something unique that it doesn't [54:44] have to do with my corporate and I'm [54:46] building and giving back to the [54:48] community then it can be published as [54:50] public and everyone can benefit from [54:52] that. [54:54] Dockerhub is the public registry that [54:57] anyone can use. So that's the most [54:59] famous registry that is available to [55:01] date. [55:04] when needed we can pull images to the [55:07] host from the registry. So this is going [55:10] to be within the host and then we can [55:15] pull images if we need them. For [55:17] example, this is a brand new host and I [55:19] would like to start an Ubuntu container. [55:22] So then I need an Ubuntu image or engine [55:24] X or Apache or whatever. And users can [55:27] also push their created images to the [55:29] configured registry. So again I am [55:31] pushing from the host out or I'm pulling [55:34] into the host. So pushing and pulling [55:37] images. [55:40] We put all of that in one page so it [55:43] becomes easier for us to deal with. Then [55:46] we have the client. We have the host [55:48] with the docker demon. We have the [55:50] registry where we have all the images [55:53] that we need if it was docker hub or it [55:55] could be a private registry for the [55:56] corporate. So we have all the images we [55:59] need for the corporate. So most probably [56:01] we have built them and now we are using [56:03] them. [56:05] So if I have a docker pull command [56:07] issued by the client, the request will [56:09] go to the demon. The demon will head to [56:11] the registry. If it is not available on [56:14] the host, then it will head to the [56:15] registry to see if we can find it. Let's [56:18] say for example I wanted docker pool. I [56:21] wanted to get an Ubuntu and a Postgress [56:25] uh database. [56:27] Then the docker pool will bring in these [56:29] images and they are going to be on my [56:31] host download them on my host. [56:34] Now since I have them then I want to [56:36] start building the container. So I can [56:39] do docker run and docker run will go [56:41] through the demon again from the client [56:45] and we'll use the images that we have [56:47] downloaded to create uh an Ubuntu [56:49] container and a Postgress container. [56:54] And of course, if you have the Docker [56:56] files, we can build our own images as [56:58] well. So that is something also we can [57:00] do. And the request will go to the [57:02] demon. The demon will know which Docker [57:04] file will pull it. And then we'll create [57:05] an image. And then I can push the image [57:07] into the registry. As you might have [57:10] guessed it. [57:17] All right, let's find out how Docker [57:20] works inside the host. Remember when we [57:23] said that the Docker demon is [57:26] how it manages or is the entity that is [57:29] supposed to manage create the images, [57:32] push the images, deal with the [57:33] registries, understand what's coming [57:35] from the client and manage networks and [57:38] containers and volumes and and so on [57:40] within the host. So does it have any [57:43] assistance? Let's find out. So [57:46] understanding how do works inside the [57:49] host. So the CLI will communicate with [57:52] the docker demon or the docker server [57:54] which is abbreviated dockerd. [57:58] Then what would docker d do? Dockerd [58:01] will process the api request coming from [58:03] the client and it will utilize [58:06] containerd functionality. So there is a [58:08] component within the demon that is [58:10] containerd to manage the container life [58:13] cycle. [58:15] Then [58:17] it does containerd itself create and [58:20] kill the containers. [58:22] So the containerd will manage the [58:24] containers will manage the storage and [58:26] will manage the networking relevant to [58:28] the containers and it pushes and pulls [58:30] images. So the containerd will function [58:34] within the demon in order to push pull m [58:37] messages manage containers storage and [58:40] networking. Then we have something [58:43] called run C and that is like lower [58:46] closer to the container which will [58:48] create and run the containers. So now we [58:51] have the CLI, we have dockerd, we have [58:54] containerd and we have run c all [58:56] together are going to be within the [58:58] docker engine inside the host and these [59:01] are the components that work together [59:03] behind the scenes. I don't see that in [59:06] order to make sure that our requests to [59:09] build images are fulfilled. Our requests [59:11] to push or pull images are fulfilled. [59:14] Our requests to build containers, to [59:16] stop them, to terminate them or to build [59:18] volumes and storage or networking are [59:21] all understood and they are fulfilled as [59:25] well. [59:31] So let's go ahead and set up the [59:33] environment that we are going to use and [59:35] we are going to do it in AWS. I know a [59:38] lot of you are going to push back and [59:40] say why not on my laptop I can't do this [59:42] v virtual machine I can't do virtual box [59:45] I can't do this I can't do that I have [59:46] my reasons so let's discuss that first [59:49] and then at the end it's up to you all I [59:51] need is a virtual machine that will be [59:52] the docker host and we're going to do [59:55] all of our labs on that host [59:58] now why AWS why do I prefer to do it in [60:01] the cloud if you if you want to do it in [60:04] Azure if you want to do it in GCP that's [60:06] fine as [60:07] My point is let's do it in the cloud. [60:09] Let's do it in the environment where you [60:11] are going to be interviewed and asked [60:14] question about and also that when you [60:17] defend the fact that maybe you don't [60:19] have actual experience in docker or in [60:23] cloud or in devops [60:25] then you can at least say that I have [60:28] created these projects in the cloud. So [60:30] you know how to deal with the cloud. If [60:31] they ask you about AWS or Azure or [60:33] Google Cloud, then you know and you have [60:36] dealt with it. It's not a black box for [60:39] you. So let's go through why I think [60:42] working in the cloud is way better than [60:45] an isolated environment or a sandbox. [60:48] First of all, you are practicing in real [60:51] world environments. environments that [60:53] you are going to see and touch when you [60:55] work in your actual job after you get [60:59] it. [61:01] It's much faster and much cleaner to set [61:04] up and delete. So let's say you bring up [61:06] a virtual machine that will be your [61:07] Docker host. Whatever happens and that [61:10] virtual machine is trashed then you can [61:12] in two minutes launch another one. [61:16] You can build confidence, personal [61:18] confidence, technical confidence in [61:20] working remotely and collaboratively as [61:22] well. In today's IT, you could be [61:25] working with the team in your corporate, [61:27] but they are in Japan for example and [61:29] you are doing something for them in the [61:31] cloud in Japan and you are in the US or [61:33] you are in Europe. Then the confidence [61:36] of working remotely and connecting to [61:38] your infrastructure remotely and [61:39] building that remotely is going to be [61:41] gained as opposed to this is my Windows [61:44] laptop. I'm going to do stack work stack [61:47] overflow and find out how to do a VM but [61:50] then the mouse doesn't work. I cannot [61:51] copy. I cannot do this. I cannot do [61:53] that. And we have lived through hell [61:55] through other courses with other [61:57] instructors in our academy about virtual [62:00] box and the compatibility for the [62:02] different and the resources and the M1 [62:04] on Mac books and all that stuff [62:07] and then you are going to master the [62:09] glue between tools. when you do anything [62:12] the cloud is going to be there in [62:14] today's it in I would say 70 80% of the [62:17] cases the cloud is going to be there [62:19] some are on premises still so when that [62:22] happens then you will be already using [62:25] the cloud using the pipelines using [62:28] other tools in the cloud and this is not [62:30] new to you [62:32] Linux operating system you are going to [62:34] be practicing on Linux operating system [62:36] all the way throughout the course and [62:39] again you can defend send your project [62:41] and your GitHub port uh port portfolio [62:44] for the projects you have done when you [62:46] are asked but yeah but you don't have [62:47] practical experience then you can reply [62:51] back and say yes but I have done that in [62:53] the cloud and I have done that with real [62:56] environment and these were not sandboxes [62:58] or isolated or following a dumb script I [63:02] have worked myself from scratch on my [63:05] projects and I have done everything from [63:07] the ground up [63:11] and most importantly because this is why [63:13] a lot of people they push back on any [63:15] environments in the cloud is cost and it [63:19] is free whatever we are going to do [63:21] throughout this course. If you have a [63:23] brand new AWS account, you will get the [63:26] resources that we are going to use in [63:28] this course for 12 months for free. And [63:31] I'm going to tell you exactly what are [63:34] the free tier services you are going to [63:36] enjoy for 12 months without having to [63:39] pay a penny to AWS as long as you don't [63:42] cross the monthly limits that I will [63:44] explain in a different video. All right, [63:46] so hopefully that has convinced you to [63:49] start doing this. All you need is a [63:50] credit card. And in the next video, I'm [63:53] going to tell you how to create the AWS [63:56] account. [63:58] What about if you cannot or you do not [64:00] want to create an AWS account? You don't [64:02] have a credit card. You don't want to [64:04] use your credit card. You don't trust [64:06] me. You think that they're going to [64:07] charge you. You want to do it on your [64:09] laptop because you just bought it and [64:10] it's new and you're happy with it and [64:12] you would like to get a return on [64:15] investment on what you have just paid [64:16] off. Whatever the reason is, there are [64:18] alternatives. Although you will be [64:20] missing on all of these points except [64:22] for the Linux OS but other than that [64:24] it's not going to be real world [64:26] environment. It's not going to be fast [64:28] to implement. You may run into issues [64:32] and it doesn't have to do with real [64:34] world environment. So it's up to you at [64:36] the end. [64:37] So what are the alternatives? The [64:39] alternatives are Docker Desktop Personal [64:42] and this works for for Windows, Mac and [64:44] Linux. And if we click on this link, [64:47] it's going to take us there. [64:49] So you have the number one [64:50] containerization software developers and [64:52] terms and if you want to choose plan of [64:55] course we are not going to pay for that [64:56] because there is one that is free. The [64:58] docker personal is free as you can see [65:01] and you can get started and then you can [65:03] follow fill in your information whether [65:06] it is personal or workrelated. Fill in [65:08] your profile or maybe login with GitHub [65:11] or Google and then you will follow that [65:13] to download it and install it on your [65:15] machine. Let me know if you need any [65:17] help with that. I can help you with that [65:19] as well. Why I did not include a video [65:22] for that? Because I am opposing that [65:26] direction. But it's your freedom. Do [65:28] whatever you want. Let me know if you [65:30] need help and I can post a video about [65:32] how to install it. So this was the first [65:35] alternative. The second one is on your [65:38] laptop. You can also do a VM, a virtual [65:42] machine. So you have a Windows laptop or [65:44] Mac or whatever, you can carve some of [65:47] the hard drive and then you can download [65:50] Oracle Virtual Box and you can start uh [65:53] creating containers and this is from [65:56] Oracle and this is where you get it [65:58] from. [66:00] So Oracle Virtual Box and then you can [66:03] download based on which platform you're [66:05] going to use it for. You can even do it [66:07] on Ubuntu and other Linux distros as [66:11] well. So, choose the one, download, [66:13] follow the steps, and then you will [66:15] install it. This one is a little bit [66:17] tricky for the mouse and copying and all [66:19] that, but definitely you can at the end [66:23] get it done. Again, I'm not opposing, [66:26] but I'm recommending don't waste your [66:28] time on that. You need to learn Docker, [66:30] not how to set up virtual boxes, which [66:32] you are not going to do in real life. [66:34] And it is free on on the cloud, on [66:36] Azure, on AWS, on Google Cloud. Choose [66:39] the cloud that you want. It's up to you. [66:43] So what are the options we have? We have [66:44] the virtual machine from VMware [66:46] Workstation and that works on Windows [66:48] and Linux. And again if you click on [66:50] this you will go to the website where [66:53] you can start downloading [66:56] Fusion or Workstation depending on the [66:58] platform that you're going to use. So [67:00] this one is uh Fusion Pro for Mac and [67:03] you have VMware Workstation Pro for PC. [67:06] So choose depending on your device and [67:08] you can follow the steps and install it [67:10] again to your liking. But what I [67:13] guarantee you in all of these cases is [67:15] it's going to waste time. It's going to [67:17] take time. Maybe if you are in it and [67:20] you are proficient about about this [67:23] maybe half an hour, 20 minutes, 1 hour [67:25] and if you are not maybe it will take [67:27] you days and it will stop you from [67:28] proceeding with learning. So again I go [67:31] back to the benefits of using it in the [67:34] cloud for free. All right. Now since we [67:37] are going to do most of our hands-on lab [67:39] and practice in AWS in the cloud, we are [67:42] going to work extensively in the cloud [67:44] in this course and that will be a great [67:46] opportunity for you to learn the cloud [67:48] as well while you are learning the IT [67:50] fundamentals. So what we'll do is we are [67:52] going to create an AWS account free. [67:54] Don't worry, you will not have to pay [67:55] anything. And that will make it easier [67:58] if you have an old laptop. If your [68:00] laptop is busy or not performing, it's [68:03] um full. The desk is full. You don't [68:05] have to upgrade to another laptop. Just [68:07] continue to use it in the cloud. That's [68:09] it. So, what do we need to do? We need [68:11] to go to aws.mazon.com. [68:14] aws.mazon.com. [68:17] And you will get a page like this one [68:19] where you click on create account. So, [68:22] we need to open an account. We have to [68:23] have an account in order to use AWS [68:26] services. [68:27] So I'm going to click on create. [68:31] And this is a free account from here. [68:33] Get started for free. And this will tell [68:36] you about the the options you have. You [68:39] have a free plan. You have a paid plan. [68:41] What's the difference between the two? [68:43] The free plan is an account. It doesn't [68:46] give you access to all AWS services. So [68:48] there will be some services that you [68:50] will not be able to use. [68:52] and scaling of services is going to be [68:55] capped. So when you are working and you [68:58] are trying to scale and do like advanced [69:02] stuff, [69:03] it will not scale accordingly because [69:06] there are some thresholds based on the [69:08] credits. So these are the disadvantages [69:10] and the account is going to be closed [69:12] after 6 months from creation. [69:15] You will receive $100 credits as soon as [69:21] you open the account. So you can use AWS [69:23] services worth $100 US. If you use them [69:27] in one month, that's it. The account is [69:30] unusable. You cannot add credits unless [69:32] you change it, upgrade it into a paid [69:35] plan. [69:37] And there are some activities that if [69:39] you do exploring some AWS services and [69:42] if you do them within the six months, [69:44] you will get another $100 credit. So [69:46] you'll have $200 credit and that's a lot [69:49] of money for someone who's learning AWS. [69:51] I mean that could easily help you do a [69:54] lot of AWS stuff that would take a year [69:57] to to work on [70:00] and you you'll have free usage of select [70:03] services and there's no charges [70:05] whatsoever. So if you are worried about [70:07] incurring any charges that will be the [70:09] account but of course you have [70:11] limitations. You can always upgrade [70:13] within the six months to the paid plan. [70:17] And in the paid plan the same thing you [70:19] get 100 credits and another 100 if you [70:21] do the AWS services exploration includes [70:24] free usage. You can scale and all that [70:27] but you are going to be charged if you [70:29] go beyond the thresholds. [70:33] workloads can scale beyond credit [70:35] thresholds because it's paid. You will [70:36] pay for it and you have access to all [70:38] AWS services. If you need to know more [70:40] about the differences, there is a an [70:43] FAQ. So these are services that are [70:45] available in both and you can keep [70:48] exploring which services and you can [70:50] always click on show more and it will [70:52] tell you if this is available in both or [70:54] not [70:56] and [70:59] you will get an yeah this is the FAQs [71:04] and in the FAQs they will tell you about [71:07] so here the free plan accounts paid plan [71:10] accounts earning additional credits what [71:12] you need to do exactly and what are the [71:14] activities that you need to do in order [71:16] to explore that. [71:20] How do I earn additional free credits? [71:22] And you go through this console home [71:24] walk through and dashboard and you can [71:26] find out what needs to be done. So, you [71:29] have everything you need and you can [71:31] find it by yourself without having to [71:33] ask me for any questions regarding these [71:35] accounts. All right, let's go back to [71:37] creating the account. [71:40] You need to write an email [71:42] that is going to be the communication [71:44] between AWS and you for bills and for [71:46] updates and so on and a nickname of your [71:49] choice for the account. So once you have [71:51] entered the email and the nickname click [71:53] on verify email. So what they will do is [71:56] they will send you a verification email [71:57] to ensure that this email is an active [72:00] email and you have access to it. And [72:02] once you verify you will be taken to the [72:04] next step. [72:07] So once you enter the email and the [72:09] name, you will get into this capture [72:11] where you have to do the security [72:13] verification. [72:15] So go ahead and do it and then click on [72:17] submit. [72:19] Once you do the capture, enter a code [72:21] that was sent to the email that you have [72:23] specified. So you need to get that code [72:26] from the email and enter it here and [72:28] then click verify. And as you can see [72:32] the email has been verified now. Now, [72:35] now you need to configure the root user [72:37] password. Basically, the username will [72:40] be the email that you entered and this [72:42] will be the password. And this is the [72:43] most powerful user in your account. So, [72:46] you have to be very careful and it's [72:48] better to use a password phrase, not an [72:50] easy to guess password. And the [72:52] conditions are available here. [72:55] It has to be at least eight eight [72:58] letters uh long. at least three of and [73:01] it includes three of the following [73:03] uppercase lowerase numbers and non-alpha [73:06] numeric characters. So go ahead create [73:09] your password and confirm it and click [73:11] on continue. [73:15] You have the two options that we talked [73:17] about the free and paid. It's up to you [73:20] if you don't want to be charged under [73:22] nor circumstances, but you're okay that [73:24] you you will bump across some services [73:27] that you are not going to be able to [73:29] use. And of course, for this course, the [73:31] free plan is more than enough. I would [73:33] go with the free plan for now. [73:40] Now, you need to select what will be the [73:42] use of this account. So, I'm going to [73:44] click on personal. [73:47] Put all the details, [73:49] your personal details. It has to be [73:51] accurate. The phone number has to be [73:52] accurate, the country and all that has [73:55] to be accurate because they are going to [73:56] send you a code to your phone and you [73:59] will need to verify it. So now they have [74:00] verified the email. They will need to [74:02] verify the phone number as well. So fill [74:05] this and after you do then takeick this [74:10] box and click on agree and continue. [74:15] Now you will need to enter credit card [74:18] information. You might be wondering why [74:21] is AWS asking me for a credit card if [74:24] this is a free plan. Simply they need to [74:26] verify your identity in three different [74:28] ways. Email was one, phone was another. [74:31] And now credit card information. That [74:33] means they know you. they can verify and [74:36] there is no way you can have wrong [74:38] information entered here because they [74:40] will check and probably they will hold [74:43] like a dollar one euro or a small amount [74:46] only hold they are not going to charge [74:48] it and it will be released in a few days [74:50] but this makes them sure that there is a [74:53] payment method just in case in the [74:55] account and if you upgrade to a paid [74:58] plan then any extra charges are going to [75:01] be charged to this credit card if you [75:03] are on the free plan they will not [75:06] charge you. So don't worry about that. [75:07] But you have to enter this information. [75:09] There is no way out of this. [75:12] So fill this information and click on [75:14] continue. And I will see you in the next [75:17] page. [75:19] Now is the sign up for AWS. You need to [75:22] confirm your identity. And now they have [75:25] given you an option. They can either [75:28] call you and give you a code or you can [75:31] receive a text message. So, both of them [75:34] are used to verify that this phone is [75:36] yours. So, go ahead, fill in the [75:39] information and click on send SMS or you [75:43] can have a voice call if they want to [75:45] call you and give you the code. Either [75:46] way, fill in the number, click on send, [75:49] and then they will text you or they are [75:52] going to call you depending on your [75:54] choice. Go ahead, do this step and I'll [75:56] see you in the next page. [75:59] Now you are faced with another capture [76:02] and then they will send you the [76:04] verification or the verification code or [76:07] the text message. So you have to fill [76:09] this capture and then you will get the [76:11] code. [76:13] All right. So this is the page and [76:15] you'll get the code. Enter it here and [76:16] click on continue. Okay. So I got the [76:19] code. It is 5320. [76:22] 5320. [76:25] Continue. [76:27] Okay. In my case, because my um credit [76:31] card, my phone number and all that [76:34] exists already [76:36] on AWS, they are refusing to give me a [76:39] free plan and they will upgrade me to a [76:42] paid plan. So, anyone who created an [76:45] account before in the good free tier all [76:48] times where we could create five 10 [76:50] accounts and use free tier in all of [76:52] them for 12 months, this is not the case [76:54] anymore. you need to use a new credit [76:56] card, a different phone number if you [76:58] would like to get around and have [77:00] another free tier. In your case, this [77:02] shouldn't be a problem because if if you [77:04] are a newbie to AWS, this page will not [77:07] appear to you. So, in my case, I'm going [77:09] to say okay, I agree. [77:13] I'm not eligible for the free plan [77:14] anymore. Anyways, I'm going to click on [77:16] confirm because I want to show you the [77:19] rest. So, that page will not appear in [77:20] your case. Now, we come to the support [77:24] plan. Leave it to the basic and click on [77:27] complete signup. All right. So, I'm [77:30] going to click on that [77:34] and guess what? Congratulations. You [77:37] have an AWS account right now. Click on [77:40] go to AWS management console. All right. [77:42] So once you log in that means you're [77:44] going to the management console. This is [77:46] the portal. This is the orchestration [77:48] and automation and management tool in [77:50] AWS. So I'm entering my account right [77:53] now. All right. So, let me take you [77:55] through a walkthrough of the AWS [77:57] management console to help you get [77:59] familiarized about the AWS management [78:01] console, how to use it and all that. [78:03] Let's go ahead. [78:06] Okay. So, this is these are few [78:07] messages. If you'd like to go through [78:09] them, [78:10] that's okay. For me, I'm not going to go [78:12] through them. Let me make this a little [78:15] bigger. So, this is the console home for [78:18] a brand new account. So this is an [78:21] account which doesn't have any recently [78:22] visited services or anything. If you [78:26] click on this side, you'll find the [78:27] account ID. You can go to billing and [78:30] cost management where you can look at [78:33] your bills and find out your consumption [78:36] and so on. [78:38] You can sign out and here you can see [78:41] that you have all the AWS regions. So by [78:44] default it has chosen for me this as the [78:47] default the one in Stockholm in Sweden [78:50] but you can switch to a one closer to [78:53] you because that will help you with the [78:55] internet latency. If you want to play [78:58] with an AWS service, work with an AWS [79:00] service, then you can click on here and [79:04] you can see that you have here a list of [79:06] AWS services [79:08] or if you know the service that you are [79:10] going to work with. For example, in this [79:12] course, we are going to work a lot with [79:13] EC2. This is the service that allows you [79:16] to create virtual machines in AWS, [79:19] virtual servers in the cloud. Basically, [79:21] if you would like to launch your own [79:24] presence in AWS, you have to create what [79:27] we call a VPC or virtual private cloud. [79:32] There are some services under VPC that [79:33] are created for you by default. You [79:35] don't have to do anything about them and [79:38] they are there for you. AWS assumes that [79:40] this is like um common denominator that [79:43] most of the people who are learning [79:45] might need it and they volunteer and [79:47] they create it for you. We're going to [79:49] learn more about this later on. If you [79:51] go into one of these services, I'm just [79:54] going to show you how it looks like. You [79:56] don't have to know anything about it [79:57] right now. [79:59] So, usually you have the dashboard. So, [80:01] this tells you where exactly are you [80:03] right now. So, I'm in the VPC dashboard, [80:05] virtual private cloud dashboard. And [80:07] these are the settings that I can choose [80:09] or the stuff that are under the VPC. [80:13] When you choose one of them, what you [80:14] see on the right hand side will be the [80:16] details of what you have selected. So [80:17] for example if I click on this these are [80:20] the subnets under subnet VPCs this is [80:23] the existing VPC root tables these are [80:26] the existing root tables. Now let's go [80:28] to EC2 which is the virtual machines in [80:31] the cloud [80:36] and as you can see this is the service [80:39] here is the EC2 dashboard as it says [80:42] instances means virtual machines and [80:45] instance types and launch templates and [80:46] there's a lot of configuration stuff [80:48] that also fall under the EC2 dashboard [80:51] for example if I wanted to create a [80:53] virtual machine and you will be amazed [80:55] at how fast you can do that. So I click [80:58] on instances. I don't have any as you [81:01] can see, but I can choose to launch one. [81:05] So this is the page that at the end when [81:08] you fill in all the information, you can [81:10] just click on launch instance and boom, [81:13] you have a virtual machine in the cloud. [81:17] So what do I need to do? I'm going to [81:19] call it first VM, first virtual machine. [81:24] And here you have the operating system. [81:26] So you can do Amazon Linux, you can do [81:29] Mac OS, Ubuntu Linux, Windows, Red Hat [81:32] Linux, Suzi Linux and so on. So there [81:35] are plenty of operating systems you can [81:37] run on the virtual machine. Remember [81:39] that the virtual machine needs a full [81:40] guest OS [81:43] and after that I will leave it to the [81:44] default. So I'm assuming that I'm going [81:46] to go with an Amazon Linux one. Any [81:49] virtual machine has a v-neck, virtual [81:52] memory, virtual desk, virtual CPU, and [81:55] so on. So if you look here, you'll find [81:57] that this is T T3.micro. That's the size [82:01] of an instance or a virtual machine. And [82:03] it comes prepackaged. So the T3 micro [82:06] will always have two vCPUs, one gigabyte [82:09] of memory, and here it tells you the [82:12] prices per hour if you use it. So in my [82:14] case, I'm going to choose let's see if I [82:17] can get to a smaller one. That's fine. [82:19] That's the least I can do. [82:22] So T3.no [82:25] keep pair. If you would like to access [82:27] the instance remotely, then you have to [82:30] create a key pair. Otherwise, I can do [82:32] proceed without. We're going to explain [82:34] that later on. Network settings, which [82:36] VPC or where it's going to land. I'm [82:40] going to leave everything to the default [82:41] now because I'm just explaining that to [82:43] you. Security [82:46] and once you are done with all of this, [82:48] all you can do is launch instance. [82:51] And congratulations, this is your first [82:54] virtual machine in the cloud. [82:56] Successfully initiated launch of this [82:58] instance. And if you click on that ID, [83:02] you get to here and you will see that it [83:04] is running and we have created a virtual [83:07] machine. Of course, as you learn the the [83:10] the particulars or the specifics about [83:12] each one of the attributes that we [83:14] needed to configure, then probably it [83:16] will take you another 10 seconds, 15 [83:18] seconds, but you will have a virtual [83:19] machine in no time. You don't have to [83:21] virtualize your laptop. You don't have [83:24] to learn about new tools like Virtual [83:26] Box or VMware Workstation. And you don't [83:29] have to do nothing. Your laptop is asis. [83:31] You don't need to split or partition it [83:33] to include a a VM. You don't have to do [83:36] nothing in the cloud. In your case, if [83:38] you are new to AWS, it's going to be [83:40] free. You have $100 credits and you can [83:44] do some exercises and gain another $100 [83:46] credits and it's going to be there for [83:48] you for 6 months. You don't need [83:49] anything else to do. All right? And at [83:52] the end of the six months, as you [83:53] advance, you can upgrade to the paid [83:55] plan and then you start controlling your [83:57] expenses based on your usage. Basically, [84:00] you are investing in the environment [84:02] that would look like the actual [84:04] environment you are going to work on as [84:06] you specialize in your career. All [84:08] right, hopefully that was clear. What I [84:10] need to do now is I'm going to terminate [84:12] the instance because my account is not a [84:14] free account. [84:17] And once I click on that, guess what is [84:19] happening right now? You'll find that it [84:21] is shutting down and it will be [84:23] terminated in no time. The second thing [84:24] you need to do and it is recommended by [84:26] AWS is I'm going to head to a service [84:29] called IM identity and access management [84:31] or manage access to AWS resources as [84:33] they call it here and we need to click [84:35] on users or I can go into IM and I would [84:38] like to create a user that is going to [84:41] be the one that we will use from now on [84:43] in the account. Why? because it's [84:45] recommended by AWS not to use the root [84:48] account that you have used to create the [84:51] account because that is the one that has [84:53] the most privileges in your account. [84:55] It's not recommended to use that one for [84:58] the day-to-day stuff. So what I will do [85:00] is I'm going to create a user. I'm going [85:02] to call that user let's say admin labs [85:08] or or can can be just admin [85:12] and I would like to provide access to [85:13] the AWS management console. So we're [85:15] going to go ahead and do this and I'm [85:18] going to create an IM user as we [85:20] mentioned and I'm going to create a [85:23] custom password for that user. [85:29] Okay, you can click on show password if [85:30] you'd like to view it. I don't want to [85:32] share that with you. Next, do you want [85:35] to add the user to the permission or [85:36] attach policies directly? This is not [85:39] recommended. It will work, but since [85:41] this is not an AWS course, let's not get [85:43] into a lot of details. [85:46] So, administrator access, this is the [85:48] highest privileges you can pro provide [85:50] to any user. So, I have looked for [85:51] administrative and this is the [85:53] administrative access. Tick the box next [85:55] to it and then click on next. This is [85:58] the permissions that you are going to [85:59] provide to the user and create user. So [86:02] from this point onwards, this is what [86:05] I'm going to use. Now if you want the [86:07] credentials to be maintained, all you [86:09] need to do is you can download the CSV [86:11] file. It will have the this is the URL [86:14] that the user needs to use all the time [86:16] in order to log into the account. And [86:19] this is the password. The only time you [86:21] will be able to view this password is [86:22] right now. So you better download the [86:25] CSV file. And this is the user. So I'm [86:27] going to use this in order to get into [86:30] the account. And you will notice here [86:32] that the name has changed. So I'm going [86:35] to copy this and I'm going to download [86:37] the CSV file. Please save it in a place [86:39] where you know that is handy for your [86:42] case. [86:43] I saved it just in the downloads. I can [86:45] relocate it later on. And then now [86:49] I can return to the users list. I can [86:52] email that to myself if I would like to. [86:54] So I can email it to marketing [86:57] dolphinate.com and I'm going to log out [87:01] and try to login with the user and see [87:03] what happens. So I'm going to sign out [87:07] and here I'm going to use the URL. As [87:09] you can see this is the sign-in URL that [87:11] we have copied and I'm going to hit [87:14] enter now. [87:18] So if you notice now it has from the [87:20] sign-in URL it had find found out what [87:23] is the account ID. So all I need to [87:25] enter now is the user and the password. [87:34] And now I'm Oh I think I wrote something [87:36] wrong. [87:41] I think I misspelled the password. But I [87:44] checked the CSV file and I found it. [87:50] In your first signup, you will be [87:52] prompted to change the password. So [87:54] basically, the one that you have created [87:55] with the user is a one time and you have [87:59] to change it and that's a protection. [88:01] Once you change it, you are going to use [88:03] that one from that this time onwards [88:05] without having to change until it [88:07] expires. And by default, I don't believe [88:10] there is an expiry, but if there is, it [88:11] will be like 90 days or something. So [88:12] you have ample time to use it without [88:14] any issues. So, let's go ahead and [88:17] change the password. [88:28] So now you will see the difference here [88:30] on this side that it's not the course [88:32] labs anymore. It's admin at the account [88:34] ID. All right. So since we understand [88:39] how to work on the AWS account briefly [88:42] right now then let's take it to the next [88:46] step. Let's go ahead and launch an AWS [88:49] EC2 instance an Ubuntu Linux instance. [88:54] This is going to be the Docker host that [88:56] we are going to use. So this virtual [88:58] machine or EC2 instance is going to be [89:00] what we will install the Docker engine [89:02] on. And this is what we're going to use [89:04] for practicing throughout the course. [89:08] Why Ubuntu? Why Ubuntu Linux? Why not [89:11] Red Hat Enterprise Linux? Why not [89:15] um AWS Linux? Why not other dist of [89:18] Linux? Because Ubuntu is not going to [89:21] cost you anything on AWS and most [89:23] probably you can do it in any other [89:25] environment and it's available. So it's [89:27] not a licensed product that will cost [89:30] you a lot of money and that's why we're [89:32] going to go with that one. If you work [89:33] on Azure, if you work on Google, if you [89:35] work on premises or on your laptop, you [89:37] will be able to find the Ubuntu image [89:40] and you will not find complications or [89:41] cost associated with that. [89:44] So what do we need to achieve in this [89:47] hands-on lab? So here is what we need to [89:49] do. We need to get to the AWS console [89:52] and then we are going to launch the [89:54] virtual machine or the EC2 instance with [89:56] an Ubuntu [89:58] operating system, Linux operating system [90:01] and we are going to make sure that it is [90:03] the free tier and we're not going to pay [90:05] anything for that. [90:07] In any virtual machine in AWS, there is [90:10] something called a security group, a [90:12] virtual firewall that protects the [90:14] instance and allows which traffic comes [90:17] from the outside and which traffic is [90:19] allowed to go outbound or basically from [90:21] the instance outside. So for that we're [90:23] going to configure the security group to [90:26] allow everything for now. We this is not [90:28] an AWS lesson. This is not a cyber [90:30] security lesson and this is not a [90:32] production environment. So we by default [90:35] all the traffic from the instance going [90:38] out by default is allowed on any [90:40] security group and we are going to allow [90:42] all the traffic coming into the instance [90:45] at the beginning. So that's what we are [90:47] going to do and we'll configure [90:48] something called an IM RO and I'm going [90:50] to show you how to do that. All right. [90:52] So that's all what we need to do and we [90:54] are going and we're going to jump [90:56] straight in into the AWS console and [90:58] start working on this. [91:04] All right. So here I am in the AWS [91:06] console. So what do I need to do now? I [91:08] need to go into IM before we leave. So [91:12] this is the identity and access [91:13] management. If you don't know how we got [91:15] here, just type AM and then you'll have [91:18] manage access to AWS accounts. AM. Click [91:21] on that and then you will get to this [91:23] dashboard. Before I move any step [91:26] anywhere, I'm going to go ahead and do [91:29] ROS. So in the left dashboard, create on [91:32] rolls. Okay, I'm going to explain [91:34] briefly what that is. We're going to [91:37] click on create a role [91:40] for an AWS service [91:43] and we're going to choose from here EC2. [91:47] And then I'm going to scroll down, click [91:49] next. Then in the permissions, I'm going [91:52] to click SSM. [91:55] And you'll find an Amazon ECT ro for [91:58] SSM. So I'm going to pick on that and [92:01] then click next. And I'm going to call [92:04] this AM RO docker. [92:09] Okay. So I'm going to remember the name [92:11] because we need to locate it. And then [92:13] I'm going to go down and click on create [92:16] RO. [92:18] Right. And now if I look here, I'll find [92:20] the RO is right here. And if I click on [92:22] it, I'll find that we have the [92:25] permissions of Amazon EC2 RO. Let me [92:28] explain to you what that is [92:33] in AWS. So let's say this big box right [92:37] here is AWS. All right. So that's [92:41] everything, the EC2 instance and all [92:43] that we're going to do is within AWS. [92:45] And this is where the internet is. And [92:48] this is where the different users or [92:50] even my laptop that I'm using right now, [92:53] it's connected to the internet [92:54] somewhere. All right. [92:58] So what does the IM role do? One of the [93:01] methods that I would like to access the [93:04] instance in order to install Docker and [93:07] do all the labs is called SSM, systems [93:10] manager. [93:13] So what does that one do? This is a [93:15] service that sits within the AWS cloud [93:17] somewhere SSM [93:21] and any EC2 instance with an image from [93:27] AWS will have an SSM agent a software [93:32] that is installed in the AMI in the [93:34] Amazon machine image in the operating [93:36] system basically of the instance. So the [93:40] recent ones, the recent instance, the [93:42] recent versions will have that agent [93:43] installed. As soon as the agent is [93:46] installed and you bring up the virtual [93:48] machine, then it will try if it has an [93:52] IM role with permissions to communicate [93:55] with SSM, then it will establish a [93:57] connection with SSM. All right. [94:01] So what is the point of having that? The [94:04] point is this is like a pipe that is [94:06] connected between them. a session that [94:08] is communication channel open and [94:11] through that communication channel one [94:13] of the ways is I can use SSM to connect [94:15] and get to the prompt of the virtual [94:18] machine and then I can install Docker [94:20] and do all the labs. We're going to see [94:21] that next. So without the IM ro this [94:24] cannot happen. [94:27] So we need IM RO and we are going to use [94:29] it when we are creating the virtual [94:31] machine. Okay. So now we have fulfilled [94:33] the prerequisites. I have the AWS [94:36] account and I have the IM RO. Now let's [94:39] move on to creating the Ubuntu virtual [94:43] machine. Let's go back to the console. [94:48] In order to create the virtual machine, [94:50] I have to go to a service called EC2, [94:52] Elastic Compute Cloud. This is the [94:54] service through which we can configure [94:57] virtual machines in the AWS cloud. I'm [95:00] going to click on EC2. [95:05] So now I'm in the EC2 dashboard as you [95:07] can see on the left hand side Amazon [95:09] Elastic Compute Cloud and I'm going to [95:12] click on launch instance. But one thing [95:15] before we move into this [95:18] depending on your location choose an AWS [95:21] region that is close to you. [95:25] How can I do that? As you can see here, [95:27] I am now if I launch a virtual machine, [95:31] I'm going to to have it in Stockholm in [95:34] Sweden. [95:36] But then if you click on that pull down [95:39] menu, then you have if you are in the [95:42] United States, you have North Virginia, [95:44] you have Ohio, you have North [95:45] California, and you have Oregon. So if [95:48] you are on the east coast, choose one of [95:50] these. If you are on the west coast, [95:52] choose one of these. In case of if you [95:54] are in the US, go with North Virginia. [95:56] But for EC2, I mean, nobody cares. Any [95:59] one of them would satisfy that. [96:02] If you are in Asia-Pacific, choose one [96:05] that is close to you. So you have Tokyo, [96:07] Sydney, Singapore, Seol, Osaka, and [96:11] Mumbai. Right? If you are in North [96:14] America, still in Canada, then you can [96:15] go with this one. If you are in Europe, [96:17] choose the one that is close to you. So [96:19] this is Stockholm, the closest right [96:21] now. And then you have South America, S. [96:23] Paulo. So these are part of the regions. [96:26] What if you are looking for a different [96:27] region? Let's say Bahrain or uh Dubai or [96:31] South Africa. Then you can go ahead and [96:34] manage the regions and choose which [96:35] region you want to work with. So in my [96:38] case, I'm going to leave it to the [96:39] default because it found out and this is [96:42] the closest to me. Or maybe I will go [96:44] with Frankfurt. I am in United Arab [96:47] Emirates right now. So Europe is close [96:50] to me. If I was in the US then depending [96:52] when I used to live in California then [96:54] west coast will make more sense. North [96:57] Virginia anybody can choose North [96:58] Virginia without any issues. The reason [97:00] for North Virginia is all the AWS [97:02] services are first launched in North [97:04] Virginia and then they they are rolled [97:07] out into other regions in the world. Now [97:11] you need to choose which region that you [97:14] are going to be working on consistently. [97:16] What's the reason for that? [97:19] Let's say I go ahead and choose North [97:21] Virginia. I create my instance and then [97:24] next time I log in without noticing [97:26] maybe I would go based on my location I [97:29] would go to the nearest region. So that [97:32] could be Stockholm or it could be Sydney [97:34] in Australia. If that's the case, then [97:37] you're going to create that thinking. [97:39] This was in North Virginia, but then [97:43] when you move back to the US or when you [97:45] go intentionally to the US, you start [97:47] forgetting about resources you have [97:49] created in regions that you don't use [97:51] regularly. That's why please try to fix [97:54] a region and always check that this is [97:57] your default region and this is where [97:59] you are going to create your resources. [98:01] I get a lot of questions about I created [98:04] the VPC and I did the subnets and I did [98:06] this and I did that and I created [98:07] instance but I can't find them. Yeah, [98:09] because you switched the region and if [98:11] you switch the region you can't see the [98:14] resources in the other region. So for [98:16] now let's go ahead and I'm going to [98:18] create this in Europe and I'm going to [98:20] choose let's say Frankfurt. That's the [98:23] one I'm going to go with and this is the [98:25] one that I'm going to stick with. What's [98:26] the reason of choosing Frankfurt? Why [98:29] geographical proximity is important? [98:31] Because [98:33] you are communicating with that region [98:35] through internet links, right? So [98:37] chances are if you are far away, if you [98:39] are in Australia and trying to get to [98:41] the US, then it's going to take longer [98:44] and at times it becomes really boring [98:46] that you click and then you keep waiting [98:48] and waiting for the page to load. So [98:51] choose one that is close to you and [98:52] stick to it at least for now. [98:56] So now I'm in Frankfurt and I'm going to [98:58] go ahead and create a virtual machine. [99:00] Launch instance means create a virtual [99:02] machine. [99:04] And here I'm going to name it Docker [99:07] host. So I will choose the name Docker [99:10] host. It's up to you. You want to call [99:11] it George, you want to call it John, [99:13] Samantha, it's up to you. Choose a name [99:16] that makes sense to you and you like to [99:19] use it. [99:21] Then I'm going to go down. And now it's [99:24] time to choose the Amazon machine image. [99:26] The operating system and it could have [99:28] also some other components defaults to [99:31] Amazon Linux. And I'm going to go ahead [99:33] and choose Ubuntu Linux in this case. [99:36] And as you can see here, then I'm going [99:38] to go with 2404. That's the version of [99:41] Ubuntu. I don't want that. And I'm going [99:44] to create only one instance. So there [99:46] are no worries so far. [99:49] So that's the AMI. Okay. Right. Then the [99:52] instance size and it's T2 micro and as [99:54] you can see here that it has let me just [99:57] zoom in a little bit T2 micro. So it has [100:01] one vCPU 1 GBTE of memory and that's [100:04] what it has. As you can see here there [100:06] will be a charge which is like 1.5 cent [100:09] or something or.5 cent per per hour [100:12] taken from your credit [100:14] key pair name. If you want to connect [100:17] remotely to the instance, there could be [100:18] a chance that you need what we call a [100:21] secure shell, an SSH, an encrypted [100:23] connection between you and the between [100:27] your laptop and the virtual machine or [100:29] the EC2 instance. So for this, I'm going [100:31] to create a new key pair and I'm going [100:34] to choose it. I'm going to call it [100:36] Docker key. I think I mistyped that. [100:40] Docker key. And I'm going to leave this [100:42] to the default. I'm going to create the [100:45] key here. Notice what will happen now. [100:49] So, as you can see, it's automatically [100:51] going to be downloaded to my machine. If [100:55] it is a Windows machine, this is a Mac [100:57] OS machine. If there's a Windows [100:58] machine, you'll find that it is [101:00] downloading somewhere in here. It is [101:02] very important to know which path, which [101:05] folder it's going to go to on your [101:08] laptop because you will need it or you [101:11] may need it depending on how you will [101:12] connect to the machine. So please when [101:14] you see that then you can right click if [101:17] you if it is a Windows laptop right [101:18] click and find out the properties and [101:20] the path where exactly it was. Did it go [101:23] into C downloads or into a specific [101:25] folder? I'm going to show you that in a [101:27] different video so don't worry about [101:28] that. Now we are talking about my [101:30] machine is a Mac OS. So that that [101:32] shouldn't be a problem. [101:34] So I know that it is in downloads [101:36] folder. I'm going to save it. So now it [101:38] has been downloaded into my downloads [101:40] folder. All right. Next step. If this is [101:44] a brand new account like mine, then [101:48] don't worry about going into here [101:50] because they are going to be all the [101:52] same. So this is where the virtual [101:55] machine it will exist. And then for the [101:57] subnet I can just pick anyone because [101:59] they are all the same and they are all [102:01] connected to the internet and we call [102:02] them public subnets. So if this is if [102:05] you are new to AWS just choose any one [102:08] of them or just ignore it. [102:10] Auto assign public IP please don't [102:12] change this. This is very important [102:14] because we need an internet IP to be [102:16] connected to the virtual machine [102:18] otherwise you will not be able to [102:19] connect to it from the outside. [102:22] Then here is the virtual firewall that I [102:24] told you about here. [102:28] Let me wipe this out. [102:32] All right. So the virtual firewall [102:34] around the instance that we needed to [102:36] allow all traffic is what I am at right [102:39] now. [102:42] So I'm going to create a security group [102:45] and then I'm going to call it docker [102:50] SG [102:52] and what I will allow is I will allow [102:55] all traffic in the inbound direction [102:58] from anywhere. So anywhere from the [103:00] internet is going to be able to [103:02] communicate with this virtual machine [103:04] basically as if I'm disabling the [103:07] virtual firewall. That's what I'm trying [103:08] to do now. [103:13] Right. And as you can see here, the [103:14] storage for the virtual machine is 8 GB. [103:17] And I'm going I'm not going to change [103:19] that because I have a free tier. So here [103:22] is another reminder about the free tier [103:24] and what you have and what you can use [103:25] per month. All right. One important [103:28] thing to note here. What if I went on [103:31] and I I said, "Okay, fine. You know [103:33] what? I want the T3 [103:35] micro, not the T2 micro." So, I'm going [103:37] to scroll down the T3 micro here because [103:40] we have [103:42] the T2 micro available. As you can see [103:45] here, there is no free tier eligible. [103:46] So, if you decided to go with this one, [103:48] which will give you two vCPUs and 1 GB [103:51] of memory, immediately you will start [103:53] being charged this amount per hour. So, [103:57] don't do this. If you couldn't find T2 [103:59] micro in that region, you will find that [104:01] the T3 micro is going to be free tier [104:03] eligible in that case. All right? So [104:06] please be wary of that. If you choose [104:08] any other one, as you can see, there is [104:10] no free tier eligible. So these are all [104:12] chargeable from day one. So please do [104:15] not do these mistakes. Silly mistakes, [104:18] but they could cost you money. All [104:19] right. So now I have done all of this [104:22] and all I need right now is to go ahead [104:24] and launch the virtual machine. [104:32] Okay. Now let me I could have assigned [104:34] the IM ro while I was creating the the [104:36] instance but in my case what I will do [104:39] is I'm going to go ahead and you will [104:42] see that there is a virtual machine [104:44] right here and here is the ID and it is [104:47] running and it's going through some [104:49] checks initializing right now. One might [104:52] think okay but how did you get here? I [104:54] clicked on the link that appeared. If [104:56] you didn't know how to get here, all you [104:58] need to do is just to type EC2, [105:02] go back to the dashboard which is here [105:04] and then click on instances and then you [105:06] will find the running one right here and [105:09] this is the one that you need to select. [105:11] All right, you will see here that it has [105:13] a public IP address. So this is the IP [105:16] address on the instance that is facing [105:18] the internet. [105:21] So if you are on the internet, so this [105:23] is AWS and this this is the internet. If [105:26] I would like from my laptop to get [105:29] access to the instance, what do I do? [105:31] Then I need to use the public IP address [105:35] of the instance and type it on my laptop [105:39] and then do whatever I would like to do [105:41] with the instance. So that would be how [105:43] you can communicate. So because when we [105:45] are doing testing throughout the labs, [105:47] I'm going to tell you go get the public [105:49] IPv4 address of the instance and use it [105:53] in your browser to do such and such. If [105:55] I ever say that or if you you find this [105:58] statement in any of the lab scripts, [106:01] then that means I'm referring to this IP [106:04] address right here. So you need to go to [106:07] the instance to the docker host. If I [106:08] mention docker host from now on, I mean [106:11] the EC2 instance, the virtual machine [106:13] that we have created with an Ubuntu [106:16] Linux with a public IP address. So this [106:19] is the public IP address. But what is [106:20] this? This is the private IP address. [106:22] When you log into the instance, you will [106:25] see this on the instance and we're going [106:28] to see that later on. Okay. So public [106:30] IPv4, private IPv4. All right. Now I [106:34] need to attach the IM ro to the instance [106:38] to be able to communicate with SSM. So [106:40] what I will do is I'm going to go into [106:42] actions security and then modify IM RO [106:46] and let me zoom out [106:50] and I'm going to choose the docker im [106:57] update. [107:07] this. [107:10] All right. So, congratulations. Now you [107:12] have a running Docker host that has [107:14] passed all the checks. Everything is [107:16] running and all all good. What about if [107:19] I wanted to add on the IM RO while I was [107:21] creating the instance? It's very simple. [107:24] You do all the steps that we have done, [107:27] but then you go all the way down. When [107:30] you have done all of this, you go all [107:32] the way down and in advanced details, [107:34] all you need to do is when you talk [107:36] about the instance profile, you scroll [107:39] down and then you choose this and that's [107:41] it. And then you go scroll to the right [107:43] and launch the instance. So all the [107:45] steps that we have done, but when you [107:47] get here, this is usually collapsed. You [107:51] need last line you need to click on the [107:54] triangle and then on the instance [107:56] profile you need to choose the one that [107:59] you have created beforehand and choose [108:02] it and then go ahead and do launch [108:03] instance but you have to do all the [108:06] steps that we have done here and that [108:08] will be the only extra step that you [108:09] need to do. All right so I'm going to [108:12] cancel this because I don't need to [108:13] create a second one. [108:17] Let me close this tab as well. So now I [108:19] have my instance right here [108:24] and I can click on instances. I can [108:26] click on here and here is my instance. [108:30] All right. Now if you have done it the [108:34] way I have done it then there is a [108:36] chance the agent might not have [108:38] connected with SSM. So all you need to [108:40] do at that case is you do a reboot for [108:42] the instance. Reboot and it will be few [108:46] seconds and the instance will be [108:47] rebooted. Life is good. You finished the [108:50] lab for the day. So you have worked so [108:53] hard today and you would like to stop [108:55] the instance so you don't consume from [108:57] the 750 hours. What do you do? All you [109:00] need to do is tick [109:03] choose the instance state stop the [109:05] instance. So if you stop the instance [109:07] and then click on stop, you'll find here [109:09] that the instance is changing into [109:11] stopping. Takes a little bit half half a [109:14] minute 1 minute and then it will be in a [109:16] stopped state. I need to make sure that [109:18] it has stopped before I leave. Keep [109:19] refreshing the page until you see that [109:22] it has stopped. But it takes time as I [109:23] mentioned. You would like to zoom in. [109:28] You'd like to minimize or maximize this. [109:30] So you have to pull it from here. So now [109:33] I can resize this if I wanted to. But of [109:35] course there is a limit for how much [109:37] resize you can do. All right. So I want [109:40] to restart it again. All you need to do [109:42] is come here and click on start the [109:44] instance. all the time you have to take [109:46] the instance first because if you have [109:48] multiple ones you have to tell AWS which [109:50] one you want to start or stop or reboot [109:52] and so on. All right, let's now use SSM [109:56] the one for which we have created the IM [109:59] role and attached it to the instance. [110:01] Let's use it to connect to the Ubuntu [110:03] EC2 instance. Let's go ahead and find [110:05] out how we can do this. Right. So here [110:08] is my instance. If in your case it was [110:10] not ticked, all you need to do is to [110:11] tick the instance and then I'm going to [110:14] go into instance state because now it is [110:16] stopped. We have stopped this before we [110:18] finished the previous video. And I'm [110:20] going to click on start the instance and [110:22] it wouldn't take long and goes into [110:25] pending and then almost immediately [110:27] after it will go into running. But this [110:30] is still initializing. So it's not 100% [110:32] ready. However, I'm going to show you [110:35] how to connect. Let me click on this so [110:37] we can widen the page without the [110:39] navigation bar. Without the navigation [110:42] bar and I can always go back if I wanted [110:45] and I can open it again. [110:48] All right. So now I have my EC2 [110:50] instance. I have selected it and it's [110:52] initializing. Refresh to find out where [110:54] we are right now. We don't have to wait [110:56] for that. Okay. So I want to connect to [110:59] the virtual machine. Why do you want to [111:00] connect to it? Because that is going to [111:02] be our Docker host. We need to get to [111:04] the prompt of the Ubuntu Linux and then [111:07] we can start playing and down [111:09] downloading the Docker engine and so on. [111:12] So after ticking the box all you need to [111:14] do is click on connect. [111:18] Then as you can see here I have options [111:20] to connect. I have the EC2 instance [111:23] connect. This is based on SSH into the [111:25] instance. [111:27] I have session manager and I have SSH [111:30] client. These are the ones we are [111:31] interested in. So I'm going to start now [111:34] with SSM. Session manager is a [111:36] subservice under SSM or systems manager. [111:40] So I clicked on connect. Now I'm going [111:42] to click on this tab. So you have to see [111:44] that this tab is the selected one, not [111:47] this one and not this one. [111:50] After you click on this, all you need to [111:52] do this has to be in this orange color. [111:57] If it's not in an orange color and it's [111:59] in a gray color and you have some errors [112:01] here or telling you that agent is not [112:03] connected, maybe you did not attach the [112:06] IM ro into the instance. So please go [112:08] back and do this. How can you do it? As [112:11] I showed you as we did it in the video, [112:14] I'm going to go back to the instance. [112:15] I'm going to click on actions then [112:18] security modify IM RO and that's how you [112:21] get into it. So that's what you need to [112:23] do. In my case, I have done it. What's [112:25] the proof that I have done it? Because [112:27] as soon as I go into sessions manager, [112:29] this is connect. The connect button is [112:33] in the orange state. All I need to do is [112:34] click on that and you will see that a [112:37] new tab is now opening. And guess what [112:40] will happen now? A new terminal is being [112:43] connected. And as you can see on the [112:46] left hand side, you are now at the [112:48] prompt of the Linux instance. So if I do [112:51] sudo su changing my privileges into the [112:56] root privilege the highest privilege on [112:58] the Linux machine. Click enter and you [113:01] can see that I am now at the root and [113:05] then some folder here. If I click on if [113:08] I do who am I which is a Linux command [113:12] it will tell you that you are the root [113:14] you are the top. So what I need to do [113:16] now is just do a cd forward slash hit [113:20] enter and now I am at the root [113:24] and this is the IP address the private [113:27] IP address of the instance. How can I [113:30] prove it? 172.31.42.177. [113:34] If I go back here and let me just zoom [113:38] out a little bit. 172 here is the [113:41] private IPv4 address of the instance [113:44] that we are in. And this is the Docker [113:46] host instance that we created. You'll [113:48] find that the private IPv4 address is [113:50] 1723142.177, [113:54] which means that I am connected actually [113:56] to this instance. [113:59] If I want to make sure that the instance [114:01] is connected to the internet, what do I [114:03] do? All you need to do is do ping. Ping [114:06] is basically sending messages to an IP [114:08] address on the internet and finding out [114:10] if it is alive or not. So 8.8.8 8.8 [114:15] that's the Google DNS servers that are [114:19] available on the internet. So if you do [114:21] this and then I'm getting a response [114:24] without errors. So this is a response [114:26] from this IP address. So basically the [114:29] ping what it does is I'm sending you a [114:32] message are you alive? And then you [114:33] respond back to me if you get the my [114:35] message and say thumbs up. I'm okay. So [114:38] now Google is telling us that I'm okay. [114:40] What does this signify? It signifies [114:43] that your instance now or your virtual [114:45] machine the Ubuntu virtual machine is [114:48] connected to the internet. So it can [114:51] communicate with the internet. [114:55] All right. So now from the virtual [114:57] machine to the internet all clear. Later [114:59] on we're going to test from the internet [115:01] to the machine but that is not what we [115:03] need to do now. I will do a control C to [115:07] stop the command. And now we have [115:09] successfully connected into our virtual [115:13] machine using sessions manager using [115:16] SSM. This is what I'm suggesting to be [115:19] the easiest way ever. So you don't need [115:22] to worry about anything else. You don't [115:24] need to worry about downloading stuff on [115:26] your laptop. Nothing at all you need to [115:29] do. So that's the way or the the first [115:32] way to do this. [115:34] All right. So let me show you a [115:36] different way you can do it. And now [115:38] it's not going to be through SSM. It's [115:40] going to be through SSH, but again from [115:42] the console. [115:47] So let me go back to the console now [115:50] here on this tab [115:53] and I'm going to click on connect once [115:55] again. [115:57] All right. Now I'm not going to use SSM. [116:00] I'm going to use EC2 instance connecting [116:04] from the console through SSH into the [116:07] instance. So I'm going to click on this [116:11] and [116:12] public IPv4 address is such and such. If [116:15] you followed exactly what I have done, [116:17] this should work for you as well. And [116:20] the username is going to be Ubuntu, [116:23] right? So if I click on connect, see [116:26] what's happening now. A completely [116:28] different terminal is opening. And it is [116:30] not the SSM SSM is still available. If [116:34] you want to check if I do the ping again [116:40] 8.8.8.8 [116:42] you'll see that it's still working. So [116:43] this session is still working. I'll [116:44] leave it open now and working. And here [116:46] you'll find that we have a completely [116:48] different one. So now I have through SSH [116:52] I'm connected to the instance as well. [116:54] How do I know? If you can see here, this [116:57] is the Ubuntu user and it's connected at [117:00] this IP address. If I just zoom in a [117:03] little bit so you can see it. So now we [117:06] have the Ubuntu user connected into [117:08] this. And if you look at this, it's [117:10] exactly the same 1723142.17, [117:14] which is exactly the same here. If I do [117:17] Ctrl C to stop it again, 1723142 [117:21] 177. I can do a clear [117:26] And it's exactly the same. So I'm [117:28] connected to the same virtual machine, [117:29] two sessions and it's exactly the same. [117:33] You will find out throughout the lab [117:35] that I will ask you at times in the lab [117:37] scripts open a new terminal session to [117:40] the docker host. So what I mean is you [117:43] have one that is open and you are [117:45] connected to the docker host. Please [117:48] open a different one. So how can you do [117:50] that? All what you need to do is go here [117:52] and click on connect and open a new [117:55] session. It's up to you if you want to [117:56] do them both SSM, if you want to do them [117:59] both with EC2 instance connect or a [118:02] third way that I'm going to show you as [118:04] well. Different ways. All I need is yet [118:07] you are at the prompt and you can type [118:09] commands. That's all I need from you. [118:12] Okay. But if you do here, if I do exit, [118:17] this is the SSM1. Okay. So if I go here [118:20] and I do a who am I and basically I'm [118:23] telling Linux I'm telling Ubuntu which [118:26] user I'm I'm using on the machine right [118:28] now and this is SSM user. So anytime if [118:32] you are lost and you don't know which [118:33] terminal and and where did you get here [118:35] and all that just do a who am I if you [118:38] did the sudo su to elevate your [118:41] permissions and then you can do all the [118:42] commands on the machine you'll find that [118:44] if you do who am I let me do the cd [118:47] forward slash if you do a who am I here [118:50] you'll find that now you are becoming [118:52] the root so the sudo su changes you from [118:54] a normal user to the root the top user [118:58] in the machine basically [119:00] here as you can see when I did a who am [119:03] I it's a completely different answer who [119:06] am I then now it's telling you you are [119:08] the user Ubuntu but if I do a sudu su [119:14] and I do a who am I again you'll find [119:17] that you are the root so now I am 100% [119:21] the same on this terminal and on this [119:24] terminal all right so these are the [119:26] easiest two ways that you can do in [119:29] order to get to the instance from the [119:30] console. You don't need to worry about [119:32] what is your machine. Is it Mac OS? Is [119:34] it Linux? Is it Windows? Nobody cares. [119:37] Do you have to install any devices or [119:40] anything on the machine? Nobody cares. I [119:42] haven't done any commands. I haven't [119:44] even touched which SSH key that we have [119:46] downloaded. So the SSH key that we have [119:49] downloaded is going to be if you want to [119:52] access from your laptop remotely into [119:55] the machine. These two methods are [119:58] connecting from within the AWS console [120:00] into your machines. So what if I'm done [120:03] and I'm I'm done for the day and I don't [120:05] want to continue. What do I do? So all [120:07] you need to do is just close the tab and [120:10] in the SSM terminate terminate or even [120:14] if you didn't do any of that you just go [120:17] ahead to the instance instance state [120:19] stop the instance and you are done. [120:21] Colossus I'm done for the day. So now I [120:24] I can go back to the instances and then [120:26] I check here and I'll find that it is [120:28] stopping. If you do this and you are [120:31] always stopping the instance after you [120:33] are done, guess what? Now you are not [120:36] going to be charged. Even the 750 hours [120:38] are not counting. They stopped. [120:41] What you are going to be charged for is [120:45] the commulative storage for all the [120:48] instances you are using if it goes [120:50] beyond 30 GB. Now for this instance the [120:53] storage allocated is 8 GB. So I can have [120:56] a second one and a third one all in [120:58] stopped states without any problems. I [121:00] have the fourth one then the total is [121:03] going to be 32. So I'm not going to pay [121:05] for the first 30 but the second two I'm [121:08] going to pay for at the end of the [121:09] month. But don't worry we have the cost [121:11] budget. It's going to let you know that [121:13] this is what is the situation. All [121:16] right. So this is how we can do it from [121:19] the console and that should be more than [121:21] enough. If you are happy with either one [121:22] of these, stick to it and finish. We [121:25] don't want to do any laptop problems. So [121:27] finally it's time for us to install [121:30] Docker on the Ubuntu EC2 instance that [121:34] we have already created. So let's head [121:36] to the AWS console to do this. So here I [121:39] am in the AWS console. I have stopped it [121:42] earlier because we were not using it [121:43] while I was doing the other labs. Now [121:45] it's time to tick on the box and then [121:48] change the instance state into start [121:50] instance [121:52] and shortly as you can see that now it [121:55] is in the pending it will go into [121:57] running and then the checks are going to [121:59] be happening for initialization. [122:02] So what do I need to do? You have a lot [122:04] of choices on how you can get into the [122:06] instance. I'm going to use the SSM1 [122:09] because I'm already in the console. It's [122:11] up to you if you want to use mobile [122:12] exterm your Windows SSH open SSH as we [122:16] have shown in the video. If you are on [122:19] Mac or Linux, you can do SSH through the [122:21] terminal in Mac. You can do it directly [122:24] uh from Linux. However you like. The [122:26] point is we would like to be logged into [122:29] the instance or the virtual machine and [122:32] I would like to be at the command prompt [122:34] because this is where we are going to do [122:36] everything. So let's go ahead and click [122:38] on connect. if you are going to follow [122:40] what I'm doing. Session manager in my [122:43] case [122:45] and I'm going to wait until this one [122:47] turns orange and then I'm going to [122:49] connect. [122:54] Okay, here we go. So, I can go from here [122:56] and I have also taught you how you can [122:58] go from here. Either one is fine. Choose [123:00] whichever you like. So, let me do it [123:02] this time through EC2 connect. [123:06] The result is 100% the same. I want to [123:09] be at the prompt. That's all I care [123:11] about. [123:13] So, here is the information that we [123:15] have. The public IP, the private IP, and [123:18] the name of the instance. And I am now [123:20] at the prompt as you can see. All right. [123:23] So, let's clear. If you are on Windows, [123:26] on the command prompt, you'll do cls [123:28] instead of clear. CLS, one word. All [123:32] right. So, what do we need to do? In the [123:34] code files, you will find this. And also [123:37] in the PowerPoint you will find this [123:40] link. So this is where we want to go and [123:43] that's exactly where I got the VS code [123:45] and the steps. So we're going to follow [123:47] these steps. Here is the link. You can [123:49] just copy and paste the link. What if [123:51] you are looking at the instructions that [123:54] you have in this file in VS Code and you [123:56] found that it was different or some [123:58] error go to the link. The most updated [124:00] one will be to the link. If you send me [124:02] a message saying that there is something [124:04] wrong with the script or the the [124:06] commands or I'm getting an error, I will [124:07] go to the link, find the updated one. I [124:09] will send it to you. So, you can use the [124:11] link. It will have the updated [124:12] information. Let's go to the link, visit [124:14] it before we use this file. So, I'm [124:17] going to click here on the link [124:21] and it will take me to manuals on [124:23] docker.com. So, I got redirected to [124:26] docker.com under engine installation [124:28] Ubuntu. All right. So this is for [124:31] Ubuntu. Please be clear. If I go back to [124:34] anyone, I have here CentOS, Debian, [124:36] Fedora and so on to install it on these [124:40] machines. So in my case, I am have an [124:42] Ubuntu machine and I mentioned that the [124:44] reason for Ubuntu is because of its [124:47] popularity. It is open source and you [124:49] can use it on your laptop. You can use [124:51] it in Azure, in Google or in AWS or [124:54] wherever you want. So this is the in [124:56] installation docker in Ubuntu [125:00] and we have the 2404 I believe the one [125:05] that we have installed [125:07] and some instructions and then it will [125:10] start right here installation methods [125:13] there are multiple installation methods [125:14] and this is the many one and there is a [125:16] convenience script but this is for [125:19] testing and development environment this [125:21] is manual step by step so we are going [125:23] to take the steps from here And that's [125:25] what is in the AML file. We are going to [125:27] update the Ubuntu operating system. [125:29] First thing, we're going to install [125:32] prerequisite packages that will allow [125:34] apt to utilize HTTPS. [125:38] Update the GPG key for official Docker [125:41] repo. We are going to add the repo to [125:44] the apt resources and we will update the [125:47] database with the Docker packages. And [125:50] then we are going to install the docker [125:51] packages [125:53] container ID docker uh commercial [125:56] edition [125:59] docker compose plug-in buildex plugin [126:02] and then we're going to check the status [126:05] start it and we're going to validate the [126:08] status again to make sure that it has [126:10] been started enable it so every time [126:12] when we stop and start the instance it's [126:15] going to be active and then we'll do the [126:17] hello world and then we're going to do [126:20] some other commands. All right. So, [126:22] let's do this step by step. I'm going to [126:24] remove it from here, but I will be [126:25] copying and pasting from this script [126:28] which will be available to you. So, [126:30] let's go back to the terminal [126:33] and I'm going to start with the first [126:35] one which is the update. Of course, you [126:38] can try to do this. [126:42] Could not open LO file and you have no [126:44] permissions basically. So, why I have no [126:46] permissions? Who am I? [126:51] you are Ubuntu user. Looks like we don't [126:53] have permissions. So one of the two two [126:55] things either we do the command the same [126:58] command with a sudo so we have higher [127:01] permissions to implement it. That's one [127:03] thing we can do. [127:16] Lots of updates. [127:21] All right. So we are done. Clear. [127:25] The other option I have is to do sudo [127:28] su. [127:30] So now I have changed from an Ubuntu [127:33] user to a root user. So I have all the [127:35] permissions. I don't need to type sudo [127:38] before every command as we go. Okay. Now [127:41] we are going to install the prerequisite [127:43] packages. [127:44] Right. [127:48] And I'm going to do the installation [127:52] of the [127:54] key rings. [127:58] Then we'll add the GPG file. [128:03] So now I'm going to start typing without [128:05] the sudo and see what happens. As you [128:08] can see it's the same now whether I use [128:11] sudo or not because I have the [128:12] permissions as the root [128:15] mod the permissions and then we are [128:18] going to add the repo [128:23] I don't think I have copied the whole [128:26] command [128:30] all right [128:32] then [128:34] we'll do updates from the added repo [128:41] Then we're going, let me clear again. [128:43] We're going to install the Docker [128:45] commercial edition containerdio. [128:50] Yes, please continue. [128:56] As you can see, some of the familiar [128:58] stuff started showing up. [129:03] Docker compose. We're going to look at [129:05] it at the end. Dockerd [129:09] build x. [129:17] There are few packages that I have [129:19] forgot. So I going to repeat the command [129:23] but of course it will install only the [129:25] ones that we did not go through. Do a [129:27] clear again. [129:29] Now [129:31] Docker is now installed. So I'm going to [129:34] check the status of docker system ctl [129:38] status docker not long commands. [129:42] So I have docker active started as you [129:45] can see [129:48] docker.service service and it's active [129:50] and running which is good [129:55] in your case if you found that it was [129:56] not running what you can do is [130:00] you can I did control C to get to exit [130:03] um in your case you can do the command [130:05] system start systemctl start docker if [130:09] it was not running in my case it's [130:11] pointless because it's already running [130:14] and you have all that again in the [130:16] script so you don't need to worry about [130:17] that all All right. So, let's do system [130:20] enable docker. Systemct ctl enable [130:22] docker. So, every time we stop the [130:24] instance, we start it again. You don't [130:26] have to go and do systemctl start [130:29] docker. So, you don't have to do that [130:30] manual anymore. Now, it's going to be [130:32] after every reboot. It's going to start [130:35] by itself. [130:37] All right. So, how can we check if [130:40] docker is running? We can do this [130:43] command. Docker run hello world. So now [130:46] what we're doing is we are using a [130:48] docker command the first docker command [130:52] and we are building a container from an [130:54] image called hello world. Don't worry we [130:56] are going to learn all that together. So [130:58] this is supposed to type if it works [131:00] it's going to echo hello world. [131:05] See what happened now. See the sequence [131:07] of events [131:10] I did docker hello world. Then it [131:13] searched locally for an image called [131:15] hello world the latest version. It [131:17] couldn't find it because it couldn't [131:20] find and unable to find it will pull it [131:23] from docker hub. We're going to go [131:25] through all these details. I'm just [131:26] explaining very quickly. Pull completed. [131:30] So it downloaded that image and then [131:34] download newer image for hello world [131:36] latest and then hello from docker. And [131:40] now it's telling me that the Docker [131:42] client contacted the Docker demon. This [131:45] is what happened. The Docker demon [131:47] pulled the Hello World image from Docker [131:49] Hub. The Docker demon created a new [131:52] container from that image which runs the [131:54] executable [131:56] and then the Docker demon streamed that [131:58] output to the Docker client which sent [132:00] it to your terminal. Try to do something [132:03] more ambitious. You can run Ubuntu [132:06] containers with such and such. And this [132:09] is the hub.docker.com. [132:12] And now if you run the same command [132:13] again, [132:18] you will find the hello from docker [132:20] echoed here. So I ran a container and [132:24] that container has implemented the hello [132:27] from docker. Got me all these messages [132:29] which proves that docker is running in [132:32] my machine. So if I want to find out let [132:35] me clear the version of docker that I'm [132:38] running here I can do docker version [132:42] as we can see here I have the community [132:45] edition the version of docker is 28.1.1 [132:50] and [132:52] again the information repeated I have [132:54] the containerd installed and this is the [132:57] version for the containerd I have the [132:59] run c which is the actual component that [133:02] takes care of the containers. I have the [133:04] version installed. [133:07] All right. And we can also do docker [133:11] minus v if I want the short form. It [133:13] will tell me that this is what you have. [133:15] So docker version is going to give me [133:18] more details. And I can do docker info [133:20] as well which will give me even more [133:23] details about this. So let's see what we [133:25] got from the docker info. [133:29] So here is the command docker engine [133:33] plugins build x compose docker compose [133:37] and the version of docker compose and [133:40] this is the server the server that [133:42] contains the demon. So containers it's [133:45] telling me that I have two containers [133:47] right now stopped are two and image is [133:50] one. So this is the hello world and [133:52] these are the containers I created when [133:54] I did the docker run hello world twice [133:57] and as soon as it give me the output it [133:59] went into exited state or stopped state [134:02] we're going to talk about this in [134:03] details [134:05] and then we have [134:08] swarm is inactive as you can see run C [134:12] version [134:14] container D version [134:20] and the details of the machine I'm [134:22] running on. So the architecture, it's a [134:24] Linux machine. It's an Ubuntu. And [134:26] here's the Ubuntu that we are working [134:28] on. So basically that's the kernel it [134:30] will lean on. The containers will lean [134:32] on. It has one CPU, one vCPU because [134:35] it's T2 micro and we have one gig. So [134:38] here is showing almost one gig that we [134:40] have right now. And the name of the [134:42] machine is IP 17231421 [134:45] 177. Here is one very important thing to [134:49] note which is the docker area the docker [134:51] root directory. This is where docker is [134:54] installed and there will be subd [134:56] directories for the containers and for [134:58] other stuff under this path. So it's [135:01] very important to know about this. This [135:03] is a docker controlled area. So it's not [135:06] recommended that we play with it at all. [135:09] But this is where Docker exists and this [135:12] is where all the subdirectories for [135:14] everything in Docker is going to exist. [135:17] So let's inspect that directory. We're [135:19] not going to play with it, just inspect [135:21] it. [135:26] So we're going to do CD and I'm going to [135:28] go into here and I'm going to do ls. And [135:32] as you can see build kit container it's [135:35] container ID image network overlay [135:37] plugins runtime swarm temp volumes. So [135:41] these are all the directories for [135:43] docker. Again this is a protected [135:46] controlled managed by docker. So it's [135:48] not recommended that you play with it. [135:50] I'm just showing you where is docker [135:53] installed. Of course that's the default [135:55] path. You have the option to install it [135:58] wherever you want. But again in that new [136:01] path it's going to have all these [136:04] directories and subdirectories available [136:06] and that's exactly the components of [136:09] docker and how it works. Not recommended [136:12] to touch it. All right that's another [136:14] good point that we wanted to see here. [136:22] See if there is anything else worth [136:25] highlighting. [136:26] Yes. So when we did the docker version, [136:29] we had the client as well the client. So [136:32] it talked about the client and the [136:34] server. So we have both. So we have [136:37] docker version and docker info will give [136:39] you a lot of information about the [136:40] system or the docker engine that you are [136:42] running right now. All right. So now we [136:45] have docker installed and whether you [136:48] contact it through the EC2 instance [136:50] connect or remotely or through SSM it's [136:54] going to be the prompt for the system [136:55] that has docker. One important thing we [136:57] note if you connect remotely [137:01] most probably you will end up with this [137:03] as the home user directory home/ Ubuntu [137:06] very important to know the path if you [137:09] go through SSM you will not find the [137:11] home/ Ubuntu it will be just the root if [137:13] you don't know you do the print the [137:17] working directory and as you can see it [137:19] is the home/ Ubuntu in any way you log [137:22] in before you use any path do the pwd [137:25] you will find where to exist right now [137:27] in the system. So now we have installed [137:30] Docker successfully and we are ready to [137:32] roll throughout the rest of the course. [137:39] All right, so it's time to get to know [137:42] some basic Docker commands. So let's go [137:44] ahead and introduce that in slides and [137:47] then we're going to immediately apply it [137:49] in the console. So theory labs theory [137:52] labs and that's how we practice and we [137:54] verify what the information in the [137:57] theory mean exactly. [138:01] So the first command we're going to [138:02] introduce is the docker pull. If you are [138:05] in a docker host and you would like to [138:07] pull an image from docker hub. So you [138:08] don't have that image you want apache [138:10] you want engine x you want ibuntu you [138:12] want centtos. Whatever the image that [138:14] you need you don't have it locally. So [138:16] you want to pull it from docker hub. The [138:19] syntax of the command, it starts with [138:22] docker. All the docker commands start [138:24] with docker and then pull and then we [138:27] have options and what's the image that [138:29] you would like to pull. If you want a [138:32] specific version of the image [138:35] if you don't specify the tag, it's going [138:38] to pull the latest version available. [138:41] So here's an example. Docker pull Ubuntu [138:44] then it will pull the latest version [138:46] because I did not include a specific [138:49] version detail here after the column [138:52] then it's going to pull the latest [138:54] version of Ubuntu. If I want a specific [138:56] version then I'm going to docker pull [138:58] Ubuntu 20 for example 04. So that is I [139:02] want the Ubuntu image version 20.04 [139:07] 04 it will pull that specific image [139:15] say also docker pull [139:18] hyphen all tags so these are options now [139:23] Ubuntu so pull all the versions that are [139:26] available from the image Ubuntu from [139:28] where from dockerhub [139:31] after I pull an image how can I find out [139:34] if it was pulled of course I I'm going [139:35] to see some activity on the screen and [139:38] then I need to know what are the images [139:40] that I have on the host such that if I'm [139:43] looking for one that I don't have then [139:45] it will be pulled from docker hub if I [139:48] have it then activities are going to run [139:50] from the local image. [139:52] So docker images is the command we use [139:55] in case if I need to find out what [139:57] images I have and that includes the [140:00] images we downloaded from docker hub and [140:02] the images we created locally and we can [140:05] use the command docker images. It will [140:07] list all the images on the local host. [140:11] We can do docker images minus q. So it's [140:13] not going to give me all the details. It [140:15] will only list the image ids that are [140:18] available. [140:22] If I need to find out if I have any [140:24] containers available on my machine, [140:28] then I do the docker ps. But there are [140:30] some options as well. List the running [140:33] containers. If no options are pasted or [140:35] are specified, it will list only the [140:37] running containers if any or blank if [140:40] there isn't any. If I do docker ps minus [140:45] a or hyphen a that means tell me all the [140:48] containers the stopped and the running [140:50] ones. So that will give me detailed [140:52] information about each container its [140:55] status ID name and more information. So [140:59] we can do docker ps [141:02] and we can docker psyen a or I can do [141:07] hyphen all and that will list all the [141:10] containers running and stopped. So let's [141:13] go ahead and check on the docker host [141:16] what we can do with these images. We're [141:18] going to visit also the docker hub and [141:20] we can see where are these images and [141:22] how do they look like and how can I find [141:24] out about the tags and so on. So let's [141:27] go ahead to the console now do some [141:28] activity before we cruise through the [141:30] rest of the commands. So I have [141:32] connected again to the host. I'm going [141:34] to do a clear sudo su. So I will have I [141:37] elevate elevate the privileges basically [141:40] that I have. And now I'm back into the [141:44] home directory as you can see. All [141:46] right. So let me do docker images to see [141:49] if I have any images available on the [141:51] machine. And as you may have guessed it [141:54] in a previous lab when we installed [141:56] Docker we looked at the hello world when [142:00] we did docker run hello world right. So [142:02] at that time it installed this image for [142:05] me. [142:07] Now if I want another one let me say I [142:09] want to pull the Ubuntu image. What do I [142:11] do? Docker pull Ubuntu and I did not [142:15] specify any tag. So here I can specify [142:18] 24.04 for example. I did not specify [142:20] anything. I'll just do this. [142:23] And now it's pulling from library. By [142:25] default, it goes to docker.io. As you [142:28] can see here, docker.io. Found the [142:31] Ubuntu. And it went for the latest. Why [142:33] did it go for the latest? Because I did [142:36] not specify what is it exactly that I [142:38] need here in this command. Let me just [142:41] enlarge this a little bit. So I did not [142:44] specify anything here and that's why it [142:47] went on and it brought the latest one. [142:49] So let me repeat the Docker images again [142:52] and now we'll find out that we have [142:53] Ubuntu and it's the latest and here is [142:56] the image ID and it was created on [142:59] dockerhub.io [143:00] two weeks ago and that's the size. [143:04] If I do docker pull and now I'm going to [143:07] go for a specific version in Ubuntu. [143:10] Let's say 24.04. [143:17] It downloaded a newer image in this [143:19] case. So [143:22] in my case which is this one pulling [143:25] from library and digest and downloaded [143:28] the image for Ubuntu 24.04. [143:32] If I do docker images again [143:35] now I have three images. I have the [143:37] latest of Ubuntu and I have the 24.04. [143:40] And you can see the size and the one [143:43] that I had earlier as well. All right. [143:46] Now let's check for what containers I [143:48] have if any on the docker host. So we [143:51] can do docker ps and as you can see the [143:54] docker ps without options it shows me if [143:58] any running containers are available on [144:00] the host and none is available. As you [144:02] can see if I do docker ps minus a show [144:06] me everything including the one that [144:08] have are in stopped or exit state. And [144:11] as you can see, we have two and these [144:13] are the ones that we ran through the [144:16] installation of Docker from the Hello [144:18] World image and the command was hello [144:22] and that was 52 minutes ago and these [144:25] are random names that have been created [144:26] for these containers. I could also do [144:30] docker psy [144:35] all and this will show me the same [144:38] output. So if you look at this or I you [144:40] look at this, it's exactly the same. So [144:43] the minus a or the hyphen a is the short [144:46] of hyphen all. So either one will get me [144:49] to find out if I have any running [144:51] containers on the system. Now let's go [144:54] go ahead to hub.docker.com [144:56] in order to find out about the available [144:58] images. [145:01] If you go on the left hand side, you can [145:03] see Docker official images, verified [145:05] publishers, and sponsored OSS. So I'm [145:08] going to go into Docker official images. [145:12] I'm looking for images to be more [145:14] specific. And then as you can see here, [145:16] Mimachd, Engine X, Busybox, Alpine, [145:19] Reddus, Ubuntu. So this is what we have [145:22] been pulling. And you can see last week [145:24] there has been more than 4 million pulls [145:27] and there is more than 1 billion [145:29] downloads. [145:31] I'm going to click on that. [145:34] And here you can find out about [145:36] overview, quick reference, supported [145:38] tags and respective docker file links. [145:41] And if you click on the tags, these are [145:43] the available versions basically. And [145:45] you will find out what's available here. [145:52] And now you can see the tags 25.04 04 [145:58] latest [146:03] 25 24.10 24.04 [146:08] and this is the command if you would [146:10] like to pull the image. This is the [146:13] latest one of course. And if I go to [146:16] another one, a specific one like the [146:18] ones we have seen, [146:21] latest for example, here's the command [146:24] to pull it to pull it to your machine. [146:27] And if you have of course one like this, [146:30] then it will be the colon and then the [146:32] the tag. This is how you pull it to your [146:34] machine. All right. So let's go ahead [146:37] and continue our basic Docker commands [146:40] journey. Docker create is to create a [146:43] container from an image. You can assign [146:46] the container a name if you would like [146:47] to and it will be created but it will [146:51] not be started. [146:53] So let's look at an example. Docker [146:55] create and then hyphen name. So these [146:59] are the options and this is a name of [147:02] your choice and then the image and you [147:04] can also add a tag if you want to the [147:07] image. So if you don't add a tag, it [147:10] will be latest. If you add a tag, it [147:12] will be the specific version that you [147:13] need. If it's not available locally, it [147:15] will be downloaded, pulled from [147:17] hub.docker.com and then it will be [147:19] downloaded and then the container will [147:20] be created but not started. [147:26] Right? The order is very important. So [147:28] if you don't add this for example the [147:32] hyphen hyphen name they will consider [147:34] that you want to create a container from [147:36] an image called my hyphen container. It [147:39] will look for it. It will look for in [147:40] docker hab it will not find it then it [147:42] will give you an error. So the order is [147:44] very important and when you want to add [147:46] an option you have to commit to the [147:48] syntax of the option as well. Okay. So [147:51] this will create a container. Let me [147:53] just erase this. [147:55] So it will create a container with this [147:57] name from engine X. That's what it will [148:00] do. [148:02] Here's another example. Docker create [148:05] and then hyphen name my container Ubuntu [148:08] and then a specific tag. So it will be [148:11] created from this specific version. So [148:13] that is a container created but not [148:16] started. What if I want to start it? [148:19] Then we go into docker start. [148:22] docker start and then the options and [148:25] the container [148:28] and flags. So start an already created [148:31] container that is not running [148:34] and the container is the name of the [148:36] container that you have or of course you [148:39] can use the ID as well. So here's an [148:41] example. Docker start my container [148:43] assuming this was already created [148:45] beforehand as we did in the last slide. [148:48] That means please start this container [148:50] for me. docker start abcd123 [148:53] if you want to specify by the ID where [148:56] do we get the ID from from the docker ps [148:58] command and then the output will find [149:00] that or docker psy a depending if it was [149:03] running or stopped and we can start more [149:06] than one container by the names or by [149:08] the ids [149:11] all right so now what if if I have a [149:14] running container and I'd like to stop [149:15] it for whatever reason I mean it could [149:17] be troubleshooting it could be we have [149:19] prepared it and it's not production yet. [149:21] So, we're going to shut it down until [149:23] the production time comes and then we'll [149:24] bring it up again. Whatever the reason [149:26] is, you can create a container using [149:30] docker create, but it will not be [149:32] started. You can start a created [149:35] container that is not started using [149:37] docker start and you can stop a running [149:40] container using docker stop. So, this is [149:43] going to stop the container gracefully. [149:46] Gracefully means don't stop it [149:48] immediately. By default, I believe it [149:50] gives it like 10 seconds, but also you [149:52] have an option that you can specify a [149:54] longer time if you think the container [149:56] will need more time to gracefully stop. [150:01] If the process doesn't terminate by [150:04] default, then 10 seconds it's going to [150:07] stop it no matter what. You can extend [150:10] it if you would like in the options. So, [150:13] docker stop and then the container ID or [150:15] the container name. [150:17] And you can also do an option minus t to [150:21] to extend the 10 seconds. Here it's 30 [150:24] seconds and then my container. So if it [150:26] doesn't finish within the 30 seconds, [150:28] it's going to be forced to stop. [150:32] And we can also stop more than one [150:35] container if we want to. [150:39] This is not docker. But remember at the [150:41] initial lectures or we always say that [150:44] containers are nothing more than a [150:47] software process that runs on Linux and [150:49] it has a process ID. So how can we prove [150:52] this? [150:55] We have multiple Linux commands not [150:57] docker commands. They don't start with [150:59] the word docker. ps a show all processes [151:02] that are running psy a ps and then psu. [151:08] And we can combine a with U and X to [151:12] show the processes owners and if they [151:15] are not attached to a terminal and also [151:17] the process that are available on the [151:19] system. All of that we are going to do. [151:21] We are going to use the PS AUX in order [151:24] to prove to you that actually this [151:27] container or the containers you're going [151:29] to work with are nothing more than a [151:31] Linux process from the Linux kernel [151:33] perspective. So let's go ahead and do [151:36] this in the console. Let's do the docker [151:39] create, docker start, docker stop and we [151:42] are going to prove that also it is a [151:44] software process. [151:47] By the way, you have this access also to [151:51] the uh script files that I'm using and [151:54] these are going to guide you through [151:55] each step that we are doing right now [151:58] and you have access to them. So you can [152:00] repeat watch the video and repeat or you [152:02] can look at the script and you can do it [152:05] yourself without watching the video. So, [152:07] you watch the video, you understand [152:08] everything. Now, it's time to practice [152:10] and you have all the instructions what [152:12] to expect to see and all that. So, this [152:14] is more like a step-by-step guide into [152:16] doing all these labs for all these [152:18] commands. All right? So, I'll keep it on [152:20] the side. I'm going to be doing the [152:22] steps, but you can always refer to it [152:24] later on and it's going to be available [152:26] to you in the Docker commands YAML file. [152:29] I'm going to remove this now and let's [152:32] go ahead to the console. [152:34] So, here I am in the console again. By [152:36] the way, if you get into the instance [152:37] using EC2 instance connect, you have all [152:40] the right to remove this. I mean, the [152:43] good thing about this is it shows the [152:45] public IP and the private IP. In some [152:48] labs, we might need the public IP uh to [152:51] connect to the instance and other stuff. [152:53] Or if you would like to connect [152:54] remotely, you would need the public IP [152:55] as well. But in my case, I need more [152:58] screen space than the public IP. So, I'm [153:01] going to remove it. All right. So let's [153:04] now start with the docker create [153:07] command. docker create and then we do [153:10] hyphen name. You don't have to if you [153:12] don't want to specify a name. And then [153:15] I'm going to create it from image engine [153:17] x. And I'm not going to add the colon [153:19] and if I do colon latest. It's exactly [153:23] if as if I did not add anything. All [153:25] right. Remember we don't have the engine [153:27] x available. So let's see what will [153:29] happen now. [153:31] So first thing unable to find image [153:34] image engine X and it decided because I [153:37] did not include anything here that is [153:39] going to be the latest. It's not [153:40] available locally. So it's pulling from [153:43] the library engine X and you have pull [153:48] complete for different items. We're [153:50] going to discuss the details later on. [153:53] And now we have a new image available on [153:56] the host and the name is Engine X. Let's [153:59] check [154:02] docker images. [154:05] And as you can see here that we have [154:07] another image available engine x and it [154:11] has been created not here on docker hub [154:13] 7 days ago this latest version and here [154:16] is the size okay but I have created an a [154:19] container right. So how can we find out [154:22] if we have running containers? Docker ps [154:25] let me clear [154:27] docker ps we don't have any running [154:30] container. If I do docker ps minus a [154:35] and you'll find that here that here is a [154:38] container with the name count one. So we [154:40] are not getting the random names anymore [154:42] because we specified the name and it is [154:45] created 59 seconds ago and it's from an [154:49] image engine X and here is the container [154:51] ID. So you have all the information but [154:54] it doesn't say exited. Exited means it [154:57] was running and stopped. So that's [154:59] exited but created that means it's [155:02] created. So how can we start it? docker [155:06] start and then either we provide the [155:09] container one [155:13] or I could have also provided the ID. So [155:17] either the name or the ID both would [155:19] work without any issues. Now if I do [155:22] docker PS again minus a. [155:26] So now these are the first two ones that [155:28] we know about but this one is up. So [155:31] even if I did docker ps only, I should [155:34] still see it because it's up in for 21 [155:38] seconds now and the port is 80 and it's [155:40] about a minute ago it was created and it [155:43] is from engine X and it's the exact same [155:45] ID. So ends with 2450 ends with 2450 [155:49] ends with 2450. So that's the same one [155:52] that was created and it's available. Now [155:54] let me do a clear. Now let let me prove [155:57] to you one thing. We have discussed that [156:00] containers are run as software processes [156:05] or processes in Linux as a software [156:08] process. Software process must have a [156:10] software ID. How can we find out? So [156:13] let's use the Linux command ps. So [156:15] that's not starting with docker. So [156:17] that's a Linux command. And I'm going to [156:20] write a. So tell me all the processes [156:22] that are running right now. [156:26] Okay. So now this is not showing what we [156:30] want. So let's do ps aux. So show me [156:34] basically everything. [156:36] And as you can see that engine x is [156:39] running. But this is not what I'm [156:40] worried about. I'm worried I'm I'm [156:42] concerned to find out if container one [156:45] is running as a process or not. So I'm [156:47] going to repeat the same command and I'm [156:48] going to search instead of looking into [156:50] all of this. Grab find out in this [156:53] output if there is anything called count [156:56] one and [156:58] sure enough there is one container there [157:01] is a process run by the root because I [157:04] have the root privileges and this is the [157:06] process ID. How do I know that this is [157:08] the process ID? Let's scroll up [157:12] in the command output and find out what [157:14] are the different columns that we are [157:16] seeing. So user P ID and then the CPU [157:21] it's taking the memory it's taking and [157:22] so on and the status as well. So P ID [157:26] that's what I have. So we got assigned [157:28] 6551 [157:31] as the process ID and here as you can [157:34] see the process name. So engine X is [157:37] running but that's fine. Engine X is [157:39] running but I was concerned about the [157:41] container. How is the container [157:43] functioning? And that's that proves that [157:46] containers are run as software [157:48] processes. All right, back to docker. [157:52] So what do we need to do now? So we have [157:54] a running container and we have proved [157:56] that we have a running container now. [157:58] Docker ps. How can we stop it? Docker [158:02] stop and then either the container name [158:05] or the ID. Let's go with the ID this [158:07] time. [158:10] And let me do a docker ps again. Oh, I'm [158:13] sorry. [158:14] docker ps nothing running docker ps [158:18] minus a and you'll find out that this [158:22] container has exited 9 seconds ago. All [158:25] right. So that's about how you can use [158:29] docker create docker start docker stop [158:33] and we have also proven that containers [158:35] run as processes on Linux or on the [158:39] operating system. It's still with the [158:41] Docker commands. We are going to look at [158:43] the Docker exit command. What if I need [158:45] to start the container and I need to run [158:48] a specific command. Let's say it's a [158:49] Python container. So I need to start [158:51] Python 3. I need to start the Python [158:54] editor basically. Or maybe it's a an [158:57] Ubuntu and I would like to list content [158:59] of a specific directory or a specific [159:01] file. Can I pass command to a running [159:06] container? And the answer is absolutely. [159:08] If it is a running container, you can do [159:10] that not on a stopped container. So the [159:13] command is docker exit for execute [159:16] and then options. We'll see some options [159:19] and then what is the container ID or [159:21] name and what's the command and what are [159:24] the arguments for that command that you [159:25] would like to pass to the container. It [159:27] has to be a running container. Okay. So [159:30] it can be used to interact with the [159:31] container's file system or processes or [159:34] environment as if you have created the [159:37] container, logged into it, executed that [159:39] command and then looked at the output of [159:41] the command. That's exactly what we are [159:43] trying to do with Docker exec. And [159:45] here's an example. [159:47] Docker exec the container name or it [159:50] could be the ID and then the Linux [159:52] command ls and then a specific path. So [159:55] you'd like to list what is in this [159:58] folder basically or in this directory [160:00] using this command. [160:03] It's very important to notice that you [160:05] are now passing the command. You will [160:08] see the output if there is an output and [160:10] that's it. So you are not keeping the [160:12] command like an interactive shell open [160:15] where you can type extra commands and so [160:17] on. It's not the case. So when would you [160:20] use this without any options? This is [160:22] when you are running non-interactive [160:25] commands. So commands that don't expect [160:27] input from you and you don't care about [160:28] how the output would look like. So for [160:31] example, ls or cat or echo. These are [160:34] examples of what you can do. Let's [160:37] continue with options for this command. [160:39] So let's look at the minus t or the sudo [160:42] tty option. This is if you'd like to see [160:45] the output properly formatted on your [160:48] screen. [160:50] So here's an example. Docker exit my [160:53] container the container ID and here's [160:55] the command ls directory is amp. I would [160:58] like to list the content of this [161:00] directory. But here we are enabling or [161:04] adding the option minus t. Please add a [161:06] tty or a sudo tty where I can see the [161:09] output properly formatted. If you do the [161:12] previous command and this command on the [161:14] same folder, the output for this one is [161:16] going to be much more organized as if [161:19] you are inside the shell of the [161:21] container. [161:24] So it will allocate a terminal or a sudo [161:26] tty to run interactive commands like [161:28] bash and so on within the container. And [161:31] the minus like it can be written hyphen [161:34] tty or hyphen t it attaches the pseudo [161:37] tty to the container basically. [161:41] So you get access to the feature of the [161:43] TTY devices. Okay. But until now you [161:47] don't really have all the input control [161:50] and we'll see that in the lab. [161:54] Then we have the minus I option. So the [161:56] minus D gets you the proper output [161:59] attaches a terminal to the container. It [162:01] can keep the standard in open. can [162:04] interact. You can send information or [162:06] instruction or username or passwords [162:08] into the container. [162:11] And here's an example. Docker exit minus [162:14] I my container and then cat etc host [162:16] name. It's not the best example. If we [162:19] have tried for example login, it would [162:21] have been much better. Why? Because [162:23] login expects you to enter a username [162:26] and password after that. So the standard [162:28] in makes sense. Or if this was a Python [162:31] simulator, a Python 3 command for [162:33] example, then it will add the simulator [162:36] and then you can interact. But now you [162:38] have the standard in but you lost the [162:40] terminal. So you don't have a terminal [162:41] for the output. So you'll be typing [162:43] this, it goes into the container, the [162:45] container responds, but you don't see [162:47] the output. So it's kind of like open [162:49] one way off. Minus D was open for the [162:51] output, minus I is open for the input [162:53] only. [162:56] So you can do I or hyphen hyphen [162:58] interactive. It keeps the container [163:00] standard in open and allows you to send [163:02] input to the container through the [163:04] standard input. And this is good in case [163:07] of commands that would like to receive [163:11] input from you in order to complete I [163:13] mean and bash maybe login would be the [163:16] best example in this case. So you need [163:18] to enter the username and password. What [163:20] if we combine both of them minus i and [163:22] minus t? You can do hyphen i hyphen t [163:25] with a space in between or hyphen it. So [163:28] that means you're combining both [163:30] together. Keep the standard in open and [163:33] please I want also to have access to the [163:36] output or the TTY. So this case in this [163:39] case when you do this you are actually [163:41] logging into the container. So imagine [163:43] what we are doing now. We are treating [163:45] the container as if it was the Ubuntu [163:48] host or the Docker host. And now we are [163:50] logging into the prompt of that virtual [163:53] little minor tiny uh computer or virtual [163:56] machine. It's actually a process as we [163:58] mentioned. And now you get a prompt and [164:00] you can run commands in the container as [164:03] if you are on a virtual machine or a [164:05] server or on your laptop. [164:08] So in this case you are doing two [164:10] things. You're keeping the standard in [164:12] out and the output as well. So you are [164:14] opening or binding the input output [164:16] streams and you will see that the prompt [164:18] has changed. You are now officially [164:21] inside the container doing activities [164:23] inside the container. And here's an [164:26] example cat etc cell and you will you'll [164:29] see that you are you have a shell open [164:32] now inside your container and you can [164:34] interact with it. If you do the cat etc [164:37] shells so the in and out are open but [164:40] now you are only executing this command. [164:41] But if you did bin bash or bash or shell [164:45] or z shell depending on which image you [164:47] are using and what are the available [164:49] shells then you can actually get into [164:52] the prompt of the container and then you [164:53] can start working on it. This command [164:56] the cat etc shells it will tell you [164:58] which shells are available in the image [165:00] you are using. So it could be bash it [165:02] could be shell it could be z shell and [165:03] so on. So if you if you are not sure you [165:06] can just run this one. If it is Ubuntu [165:09] or most of the Linux ones, you could [165:10] have the bin bash or you can just write [165:12] it as bash. It will give you exactly the [165:15] same if bash was on the path inside the [165:18] operating system. But that's more of [165:19] Linux. This is not Docker. Okay. So [165:22] let's go ahead to the console and let's [165:25] try these commands one by one. And again [165:28] the scenario that we're going to work on [165:30] is available in the script that will be [165:32] available to you in the course [165:34] resources. So, I'm going to be looking [165:36] at the file, doing the steps, but you [165:38] can do it on your own from the file. You [165:40] don't even have to look at the video [165:41] because even the exact steps and what [165:44] what they do and why we are doing them, [165:46] it's all explained as you can see right [165:49] here. [165:51] So, taking it step by step to see what's [165:53] the difference between the minus I and [165:54] the minus T and so on. All right, let's [165:56] go ahead to the console. All [165:59] right. So, still in the console and if [166:01] you recall, we ended up with container [166:05] one and we have jolly deviian and [166:08] anyways I mean these are the old ones. [166:10] If you want to clean up everything we [166:12] can do that simply with the docker rm [166:15] and then the name of the container for [166:17] example. So docker rm if I do docker ps [166:20] minus a again you'll you'll see that [166:22] container one is gone. And I can also do [166:25] it by the ID docker rm. And then I can [166:29] copy the ID. [166:31] And I can do more than one at the same [166:33] time. [166:35] So now I'm going to delete both the [166:37] other containers. If we check again, I [166:40] don't have any containers. Nothing [166:43] running and nothing stopped. Clear. [166:47] Okay. And for the images, what this is [166:49] what we have. We have Ubuntu, the latest [166:51] 24.04 04 and the hello world latest. [166:55] What if I want to delete an image? So I [166:57] can do docker then I can do rmi remove [167:02] image and I can then take this one for [167:06] example. [167:08] So the hello world now is going to be [167:10] removed. [167:13] All right. So if I do docker images [167:15] again, [167:20] now I have only the two Ubuntus. All [167:22] right, let's now start what we wanted to [167:25] do. We want to try and see how can we [167:27] execute commands inside the container. [167:30] So for that, let's go ahead and create a [167:32] new container [167:35] and I'm going to call it container 2 for [167:39] a change and this will be from an engine [167:41] X image. Okay, so now I don't have [167:45] engine X locally that's why it's being [167:47] downloaded now the different layers of [167:49] the image. We'll talk about layers later [167:50] on and as you can see there is an ID for [167:53] each one and if I do docker images now I [167:56] should have engine X available as well [167:59] as you can see. So I have engine X and [168:01] it is downloaded and so on. All right so [168:04] let's do a clear. [168:07] So now we need to start the container. [168:11] start container 2 [168:14] docker [168:15] ps and as you can see we have the [168:18] container up and running container 2 up [168:20] 3 seconds ago and it was created 35 [168:23] seconds ago and it's engine x and this [168:24] is the container ID allocated okay [168:26] excellent so let's execute a cat command [168:29] on the container so exit no options [168:33] container 2 and I'm going to do cat etc [168:38] host name [168:40] and here is a host name that is [168:42] available in the container but again now [168:45] the container if I do ps container is [168:47] still running I executed that command [168:49] got the output and that's it so let's do [168:53] cat and let's try etc hosts [168:57] as you can see the output cat ect hosts [169:00] but then I have all of these are inside [169:03] a file called hosts under directory etc [169:06] inside the container all Right. So what [169:09] if I did docker exit minus t? I want the [169:13] output to be a little bit better than [169:14] this if possible. [169:18] And I'm going to do [169:20] exit into container 2. And I'm going to [169:22] do an ls command. [169:25] So the ls command it's kind of as if you [169:28] are inside the machine a a Linux machine [169:30] and it is properly formatted. Let's [169:35] prove it. Let's remove this and do the [169:37] same command. So exit also container 2 [169:41] ls. See the difference. So this is just [169:45] like a dump of all the output all all [169:48] what's available. But here it was [169:50] appropriately and lined up nicely and [169:53] all that. Why? Because the minus t gives [169:55] me the sudoty output. So it's nicely [169:58] formatted on the output. Okay. All [170:00] right. Let's do a clear still with [170:03] container number two. And if I do docker [170:06] ps, I still have it running. And what [170:08] we'll need to do now is we would like to [170:11] try something else. So I have the minus [170:14] t. I know that. Let's forget about [170:16] options. Now let's say that I'm going to [170:18] docker exit container 2 as well. But in [170:22] this case, I want to run the command [170:24] login. So I want to login to the [170:26] container operating system. [170:29] I would expect if I was on a Linux [170:30] machine if I am logged into the prompt [170:33] then I would get a login prompt and then [170:36] I will enter the password and that's how [170:38] it works. Let's do it. [170:40] I don't get anything. I don't have [170:43] access to the container to send in and I [170:46] don't have the output as well. So let's [170:48] change this and put the option minus t [170:51] and see what happens. See the difference [170:54] here. I didn't get anything because I [170:56] don't have any options here. I get the [170:58] output nicely formatted [171:01] and if you notice the host name is [171:02] exactly the container ID. So I'm getting [171:05] this response from the container. It's [171:07] asking me to login. So let's say I'm [171:09] going to say just anything random engine [171:11] X. I expect it to ask me for the [171:13] password and then it will tell me an [171:15] error. [171:17] There you go. So I sent it in the [171:20] container is waiting for me. I'm waiting [171:22] for the container. I don't see anything. [171:24] And why is that? because I don't have [171:27] actually a channel into the container to [171:29] send this. So, it didn't make it to the [171:31] container. And since it didn't make it, [171:34] although I have the TTY, nothing came [171:36] out. So, what do we do then? Let's Ctrl [171:38] C. Let's make sure that our container is [171:42] still running. Yeah, it is still [171:44] running. Let me clear the screen. [171:47] And now, let's do Docker exit. But I'm [171:49] going to do the interact the minus I. [171:53] So now I have sending in into the [171:56] container. I have the standard in that [171:58] will be available to me [172:00] and I'm going to still do the login. [172:05] I don't see the login information again. [172:07] So it looks like I'm sending information [172:09] into the container, but the container [172:11] doesn't have any instructions. It [172:13] doesn't have any TTY attached that will [172:15] display things for me. So what I can do [172:18] now is I can combine both the minus I [172:21] and the minus T. And let's see the [172:23] difference. Now I have this. I'm going [172:25] to type engine X. And guess what? Now [172:28] the minus T is sending me the password [172:32] because the minus I was open and this [172:34] went into the container. Of course, I'm [172:36] going to type whatever. I don't have [172:38] this username. I'm just trying any [172:40] random thing. It will take some time. [172:42] Give me an error. And we are good to go. [172:43] Login incorrect. See, I have still the [172:46] channel open with a container and the [172:47] output as well working for me. And that [172:50] was the command login. So let's do Ctrl [172:52] C now. [172:55] And I'm going to check also that it's [172:57] still running. Let me do a tricky thing [173:00] now. Let me docker. And I'm going to do [173:05] exit- [173:08] and into container 2. And in this case, [173:11] I'm going to do a cat into the file that [173:14] we discussed, [173:17] which is the ATC/Shells. [173:22] /c/shells. [173:28] Okay. Engine X does not have these [173:30] command. All right. So, let's do let's [173:32] do this. I'm going to do it blindly. I [173:34] think it will work because I believe [173:35] that Engine X has the the BIM bash and [173:37] has the the bash as well. So I'm going [173:40] to do bin bash [173:43] and of course you can write bash only [173:45] and let's try what happens. Please [173:47] notice that I am on the docker host and [173:49] this is the prompt. Uh my mistake we [173:52] shouldn't add the cat at all. I'm just [173:55] trying to start the bimbash shell. So [173:58] this should not be here. And either I [174:01] write bash or I write /bin/bash [174:10] and see what happened now the prompt has [174:13] changed from this into this and I'm a [174:17] root privilege into this host. What is [174:20] this host? If you go a little bit up see [174:23] when we got the login what was the [174:24] prompt? It was from BD2 and it ends with [174:27] 22A. And now I'm in BD2 and it ends with [174:30] 22A. So now I'm inside the container. [174:34] And let me show you one thing also here [174:37] that if you do ls, [174:39] that's exactly what we have received [174:41] before when we did the ls command. And [174:43] if we do ps here, oh okay, the ps [174:46] command is not. So we have to install [174:47] some utilities to get in here. I think [174:49] the ping is not available as well. Let's [174:52] try [174:54] 8 and ping is not available. So it is [174:57] skimmed from the essential utilities but [174:59] I will show you in a later lab how we [175:01] can install these utilities. So we'll [175:03] have troubleshooting ways inside uh the [175:06] containers when we log into them. What [175:08] if I want to exit? Just type exit. And [175:11] if you do docker ps again you'll find [175:15] that the container engine x is still up [175:17] and running. As you can see docker [175:20] ps minus a and I have only this [175:22] container. It's in up and running. All [175:24] right. So if you would like to interact [175:26] with a container in and out minus it is [175:30] your best friend. And you can write it [175:32] docker exit by the way. Docker [175:36] exit. You can write it as minus t minus [175:40] i or minus i minus t if you don't want [175:42] to combine them. And then this is [175:44] container two. And I'm going to run bash [175:46] in this in this case, not the bim bash. [175:49] And you'll see that it works. And again, [175:50] I am inside the container again. So if [175:53] you would like to do troubleshooting, [175:54] testing, installing packages, doing [175:56] whatever you like inside the container, [175:58] you can log into the container and do [176:00] that. If you don't want to login, then [176:02] you want to just ls something or cut [176:04] something. You don't need all of this. [176:06] You need the minus t just to get the [176:07] output nicely formatted. If it is uh a [176:10] command that does not need the [176:12] interaction, if it was Vim or login or [176:15] uh something else, then it's better to [176:17] have the -ash it get into the container, [176:19] do whatever you like, and then save it [176:21] and exit. And that's it. So, I'm going [176:23] to do exit. [176:26] And here I do docker ps. Okay, let me [176:31] clear [176:33] docker ps. The container is still [176:35] running. If you want to stop it, you [176:37] know it. docker stop count two and now [176:41] if you do docker ps it it's not there if [176:43] I do docker ps minus a it is there and [176:47] it has been exited by force because you [176:49] stopped it let's continue with more [176:52] docker commands and this is a very [176:54] important one docker run docker run is [176:58] equal to docker pull plus create plus [177:02] start so basically if you do docker run [177:05] and then you decide what options and you [177:07] define the image and the command. If you [177:10] would like to execute a command when the [177:13] container runs, if the image is not [177:15] locally available, it will be pulled [177:17] from docker hub and it will create the [177:20] container and it will start the [177:21] container. So this is equivalent to the [177:24] three [177:26] commands docker pull, docker create and [177:28] docker start. [177:30] Here's an example. Docker run engine x. [177:33] There is no tag here which means the [177:35] latest one. This will create and start a [177:37] container using latest engine x image. [177:40] And if you don't have these on the [177:42] docker host, then it's going to be [177:44] downloaded from docker hub beforehand. [177:49] You can add the options d-name or hyphen [177:54] name. And you can also put a tag if you [177:56] would like to [177:59] when you run a container from engine X. [178:03] And this is how you do it. and we'll see [178:05] that in the lab. Then the prompt is [178:08] going to be stuck. So basically you will [178:10] not get the docker host prompt again. If [178:13] you'd like to run the container in the [178:15] background and you get hold back of the [178:18] prompt from the docker host then you use [178:20] the minusd or detached mode. So [178:23] basically create the container from [178:25] engine x. If engine x is not in the [178:27] local host download it start the [178:30] container but please give me back my [178:32] docker host prompt. run it in the [178:33] background in detached mode. [178:38] We can also use run with the hyphen it [178:42] in order to get into the container as we [178:44] have seen before like in exit docker [178:47] exit command. [178:49] So we can do docker run- [178:52] it interactive and [178:56] terminal from Ubuntu and start bin bash. [179:00] So you will be inside the Ubuntu [179:02] container prompt or logged in and then [179:06] there will be a bin bash shell or a bash [179:08] shell basically open for you as well [179:12] and you get the interactive so you get [179:14] the input the ability to send input into [179:16] the container and you get also the TTY [179:19] with it [179:23] and it depends on if the bash was in the [179:28] path in the operating system of the [179:30] container then you can just write bash [179:32] withoutbinash. [179:35] So these two are the same but in case if [179:38] bash was not in the path then you have [179:40] to define the total path /bin/bash. [179:46] Now we have docker create and docker run [179:49] both of them they will try to locate the [179:51] image locally and if not available then [179:54] they will try to get it from docker hub. [179:56] If it's not on Docker Hub that means you [179:58] are this is maybe a typo or the wrong [180:01] name and it cannot find it and you'll [180:03] get an error. So as a workflow you can [180:05] start with docker run or docker pull [180:09] and docker will look for the image [180:11] locally. If it's not available then it [180:13] will go ahead and search in the docker [180:15] hub and as we mentioned it is by default [180:17] docker.io. [180:19] If it is on docker hub if the answer is [180:22] no then you get an error. the image [180:24] cannot be located or is not found. If it [180:27] was on Docker Hub, then you will get [180:29] into downloading the image different [180:31] layers. Then the image is going to be [180:33] installed on the local host. It will be [180:34] available. Now [180:37] if it if the command was docker run or [180:39] create then it will have to create a new [180:42] container from the image and it will [180:44] start the container if you used the [180:46] docker run. If it was only docker pull [180:49] then it will stop here. If it was a [180:52] docker run or docker create then it's [180:56] going to create the new container. If it [180:58] was docker create it will create it and [181:00] that's it. It will not start it. If it [181:02] was docker run then it will start it and [181:04] then the container will be up and [181:06] running. So docker run is the one that [181:08] does the full 9 yards. Docker pull [181:11] starts right here and docker create [181:14] starts right here without starting the [181:16] container. If the image was available [181:19] locally then it will just jump into [181:21] this. If it was a docker run or docker [181:23] create create the container. If it was [181:25] docker run then it will also started and [181:28] the container will be running. Okay. So [181:30] that's more or less what we have [181:32] discussed but in a visual format or in a [181:34] workflow format. [181:37] We have also one option if you would [181:40] like the container to run something [181:42] specific and then it will self-destruct. [181:44] So if we do this docker run hyphen rm [181:49] basically that means remove or delete [181:52] ubuntu is the image and then here is the [181:54] command that it will do echo this will [181:57] self-destruct. So what will happen here [181:59] is it will echo this sentence on the [182:02] screen and if you go and look for the [182:04] container you will not find it running [182:06] and you will not find it as well in the [182:09] exited mode. It will be deleted. [182:14] So why would you do this? Use it for [182:17] oneoff containers. So you just need it [182:19] to do something and disappear gets [182:21] deleted clean up by itself. Like if you [182:24] want to curl or ping or do some testing [182:27] function and once it's done the [182:28] container is no longer required and I [182:30] don't want to go and remove it manually. [182:32] Just remove it. [182:35] But don't use this at all if you are [182:37] talking about long-term containers. If [182:40] it is a website, a database component of [182:43] an application that needs to be up and [182:44] running all the time. [182:47] Here we have docker run it and remove [182:49] Ubuntu bash. So if we don't look at this [182:53] part, this is a normal command we have [182:56] seen before. Docker run it Ubuntu bash [182:58] that means start a bash terminal or [183:01] shell inside the container. The hyphen [183:04] rm once you exit it will be deleted. So [183:08] create and run an Ubuntu container. Open [183:10] the interactive shell into the [183:11] container. Once the user exits from the [183:13] shell, delete the container. All right. [183:16] So let's go ahead and do this in the [183:18] console. Let's work on that and see how [183:21] the Docker run acts or behaves as we [183:24] have seen with the previous examples. [183:26] All right. So let's go ahead and play [183:28] with the Docker run command. Let me now [183:30] get to the console. [183:33] So I'm going to go in. I'm going to use [183:35] EC2 instance connect. [183:38] open a new session and from the same [183:42] script that we have been using before. [183:44] Now we're going to start with the docker [183:45] run uh stuff here. Maybe the names I [183:49] will use for the containers are going to [183:50] be shorter. Doesn't matter. When you see [183:53] the names, choose whatever names that [183:54] you would like to do, but you need to [183:56] update the different commands. All [183:57] right. So, what I will do now is I will [183:59] do the sudo su [184:03] and I'm going to do a clear [184:07] I don't need this. So I can stop this as [184:09] well. So I have more space. So what are [184:12] going are we going to do? We are going [184:13] to create an Ubuntu container. So docker [184:16] run [184:18] docker run and then we need to do it in [184:22] I'm not going to do it in detached mode. [184:24] I'm going to start without detached [184:25] mode. I am going to show you the [184:26] difference between using the detached [184:28] mode or not. Okay. Let's say say name is [184:31] con one [184:34] and this will be from engine x engine x [184:40] can't find the image locally because [184:41] it's a new machine I told you so it will [184:43] download it from docker hub and once [184:46] downloaded it will start the container [184:50] as you notice right now the container is [184:53] up life is good but then I don't get my [184:57] prompt back so I'm stuck into a [185:00] container that is running now. The image [185:02] is already downloaded as you can see [185:06] and configuration was ready. [185:10] All looks good. Start worker process. [185:12] Start worker process 29. Engine X [185:14] started. Everything is cool. But then [185:16] I'm stuck. Well, that doesn't help. One [185:19] might say, but how can I believe that [185:22] the container is running? Maybe you are [185:24] just bluffing, right? So, let's do one [185:26] thing. Let's go ahead here and I'm going [185:28] to open a new terminal, a second [185:30] terminal. So this is one terminal which [185:32] is stuck and this is the second one and [185:36] I can open more than one. So it feel [185:38] free if you would like to do testing [185:40] where you do some commands on one and [185:42] then you log in from another one and see [185:44] what's going on. So let me do a clear [185:46] now. Let me docker [185:50] ps and you can see here we have a [185:53] container called container one. It's [185:55] engine X and it has been up for about a [185:58] minute. And here is the ID. So this [186:01] proves what I said that we have a [186:02] container running but I'm stuck within [186:04] the container. That's what happening [186:06] now. And here is the name count one and [186:09] engine X. So what do I do now? Then we [186:12] can exit. But if you exit that means you [186:15] have [186:16] stopped the container. [186:19] And even if I go to the other terminal [186:21] and repeat the same command, we'll we'll [186:23] see that there's nothing running. Docker [186:25] ps [186:28] minus a. You'll find that we have an [186:30] exit container 15 seconds ago. [186:34] So I'm going to leave that second [186:36] terminal for now. Maybe we'll need it [186:37] for the for the future. Okay, let me do [186:40] a clear here. [186:42] All right. So what do I do? I want to do [186:45] exactly the same, but I don't want to be [186:47] stuck in this in this case. All you need [186:49] to do is docker run minus D detached [186:52] mode and [186:55] name if you want [186:58] and if you'd like to name it that's [187:00] fine. Container can I use one? Let's [187:02] see. Let's find out if I can use one [187:04] again. [187:06] Conflict. There is an error. There is [187:09] already a container even if it was [187:11] stopped. And here's the ID that is [187:13] already with the same name. So please if [187:16] you'd like to use a name, use a [187:17] different one. That's why if you don't [187:19] use the hyphen hyphen name and you [187:21] provide a name, then there will be a [187:23] random name assigned to the container. [187:25] So let's try that. [187:27] I'm not going to assign it a name at [187:29] all. [187:31] I'm just interested to see the detached [187:33] behavior and I'm going to hit enter. So [187:35] now there is a random name assigned and [187:38] there is an ID for the container and now [187:40] I have a container running and I got the [187:43] prompt back. So I can do more commands [187:45] from the same terminal. How do I know [187:48] that docker ps and as you can see here [187:50] that we have a container running and it [187:53] is from engine x. Here is the ID and it [187:56] was done 14 seconds ago and a random [188:01] name. Basically that's what we get here. [188:03] All right. If you look here at this ID [188:08] and if you look at what we got as an [188:10] output here to the command. If you look [188:12] at the first part, the first 12 alpha [188:15] numeric characters, they will be [188:17] identical to this one. So that's the [188:18] container ID. All right. So that's fine. [188:21] So now we know about this one. [188:25] Now let's do one thing more which is [188:28] trying the hyphen it into the container. [188:31] Of course I can do docker exit [188:34] hyphen it [188:36] and I can get into this container. I can [188:39] use the name or in this case let me use [188:41] the ID for a change [188:47] and bash. So now I got into the [188:50] container and here is the ID and I have [188:53] root privileges and this is the host [188:55] name and I'm now inside the container. [189:00] I'm going to exit now. Now let's look at [189:03] docker ps again. [189:06] We still have the container running. [189:08] When you run from docker run [189:11] and you have the container running and [189:14] you get into the container and you exit [189:16] as you have seen now with docker exit it [189:18] doesn't terminate the container the [189:20] container continues. So can I have done [189:22] the same in one step instead of creating [189:24] the container and then doing the exit. [189:26] What if I I know from the beginning that [189:28] I need to get into the container. So in [189:30] that case you can do docker run- it if [189:34] you want to give it a name that's fine [189:36] but avoid an existing name or you will [189:38] get the error up to you and then I can [189:41] do engine x [189:43] and then I'll do bash. So that's all [189:46] this is this first command and the [189:49] second command in one. Can I run this [189:55] and then I can keep it in detached mode? [189:57] Yes, you can. You can add a D at the end [190:00] it or spacey D that means run in [190:04] detached mode but keep the terminal [190:07] running and please the interactive mode [190:09] I need to have the ability to send [190:12] information into the container and also [190:14] to receive the output. Okay. So now here [190:16] I can do ls and as you can see we have [190:19] lots of directories. If I go let's say [190:21] for example into the etc folder and I do [190:25] ls you'll find here that we have hosts [190:28] for example I can do cat hosts and then [190:32] you'll find the information about IP [190:34] addresses and stuff like that so for [190:36] example the container now has this IP [190:39] address but this is not the time to talk [190:41] about this I'm not going to talk about [190:43] networking now the time will come when [190:45] we'll talk about it all right so I can [190:47] do exit [190:49] now I'm outside the container. Let's do [190:51] docker ps. [190:53] I still have the container up and [190:55] running in my case. [190:59] Oh, that's the other container. I'm [191:01] sorry, that's the previous one. If we do [191:03] docker ps, I'm looking I should be [191:04] looking at container 2. So container 2 [191:08] when you do the docker run hyphen it and [191:10] you get into the container and then you [191:12] exit. See what happened now? The [191:15] container stopped. Whereas when we did [191:18] the docker the the docker run where was [191:21] it right here when we did the docker run [191:24] in detached mode and then I I got into [191:26] it into it with a docker exit it did not [191:29] terminate the container that's why we [191:31] have one running right now. So what if I [191:34] wanted to stop the other container? It's [191:36] very easy. Do [191:39] docker stop and the container [191:43] ID. So we have to do docker ps first [191:46] because we don't know the name. The name [191:47] was a random one. I can choose this name [191:49] if I want to. And then I can do docker [191:53] stop. [191:55] And if I do now docker ps there is none [191:59] working. And if I do docker ps minus a [192:02] then you'll find that container 2 and [192:04] the elastic board and container one they [192:06] all all have stopped. Let's do a clear. [192:12] All right. So let's do one more example. [192:15] So docker run [192:18] hyphen it [192:20] and then what we'll do is I'm going to [192:22] do name container 3 because I used one [192:25] and two. You can just use any names [192:27] you'd like and this one I'm going to run [192:30] it from python image and the command I [192:33] want to run once this this is uh started [192:37] is bin bash. So I'm going to get into [192:39] the shell bash shell with interactive [192:44] terminal in order to get into the [192:46] container. So notice that this is the [192:49] prompt we have right now and I will hit [192:51] enter. [192:53] The Python image is not available [192:55] locally. So it will download it and as [192:57] you can see different layers of the [193:00] image. We're going to talk about layers [193:01] later on. It's downloading one by one as [193:04] you can see and they have different [193:06] sizes. [193:10] So now what I'm doing, believe it or [193:12] not, I'm getting Python inside the [193:16] container. That's what we are doing [193:18] right now. And not only that, we have [193:20] downloaded that and also the container [193:22] has started and now we are inside the [193:26] container. [193:28] So this is the container itself. [193:31] All right. So what do I do now? Let's [193:33] update [193:37] So now I'm working inside the container [193:39] as if it is a Linux machine. If you [193:41] notice I'm using Linux command Ubuntu [193:43] commands because the container has [193:46] access to the kernel, right? We said we [193:48] are sharing the operating system and the [193:50] operating system is Ubuntu. So that's [193:52] why I'm using Ubuntu commands without [193:54] any problems inside the container right [193:56] now. But of course not the full list of [193:59] commands. This will be a many set of [194:01] commands that are available. Now let's [194:03] do apt upgrade. [194:08] Yes, I need to continue. [194:14] See package lists, dependencies, reading [194:18] state information, calculating upgrade [194:28] packing. All right, so let's do a clear. [194:31] That's too much in the screen. All [194:33] right. So what do I need to do now? I [194:35] need to do ps to see the processes that [194:37] are running. I have the ps itself and I [194:40] have bash running. So this proves that [194:42] the command we executed when we created [194:45] the container has started a bash process [194:48] inside uh the container. Okay, that's [194:51] fine. Then what do we need to do now? [194:53] Now we have Python, right? Let's run the [194:55] editor. [194:57] So this is now talking about this Python [195:00] version and this is the editor. So [195:02] Python is running. If I do 1 + 1, you'll [195:04] get the result is two. Okay, let's do 2 [195:08] * 5 and the answer is 10. Let's do [195:12] print. All these are basic Python [195:16] commands. And I'm going to do hello [195:18] world. [195:23] You'll find that it is printing hello [195:24] world. If I want to exit, I'll do this [195:26] and just the parenthesis. So now I'm [195:28] out. And if I do exit again, I'm outside [195:30] the container. Now let's do if the [195:32] container is up or or down. The [195:35] container went down. Now because we did [195:37] the run hyphen it and when we get into [195:39] the container, then you exit and it goes [195:41] away. All right. So let's do a docker [195:44] ps. So now the container has stopped. [195:46] But if you do a docker ps minus a, [195:49] you'll find that the container is [195:51] available. The python container is still [195:52] available. What if I wanted to do a [195:54] one-off job and I want the container to [195:56] disappear afterwards? So, here's what [195:58] we'll do. We'll do the another [196:00] container. Let me let me u use container [196:03] 4 for example and I'm going to use the [196:07] hyphen [196:09] rm. So, remove upon exit and I'm going [196:11] to do this and start. So, the container [196:15] is started. I am inside the container [196:17] right now. What if I do an exit now or [196:20] let me before I do this let me check [196:22] from here to make sure that it is [196:25] running. I have container 4 running as [196:27] you can see. Now if I go here and I do [196:30] exit and then I repeat the command here [196:35] I don't see anything running. If I do [196:37] minus a I will not find container 4 [196:40] exited as before. It has been deleted. [196:43] still with Docker basic commands and [196:45] we're going to look at Docker inspect. A [196:48] very good command that is used to find [196:50] detailed low-level information about [196:53] containers. You can use it with [196:54] containers. That's one usage. You can [196:56] use it with images, you can use it with [196:59] volumes, and you can use it with [197:00] networks. The output is going to be in [197:02] JSON format. So, what kind of low level [197:05] details about containers you're talking [197:07] about? What are the mounting of volumes [197:09] if there are any? What's the IP address [197:11] that the container has? and a lot more [197:14] information about that as well. So this [197:16] is for the containers. How about the [197:18] images? The details of the image, layers [197:20] of the image, volumes, tell me details [197:22] about the volume, the size of the volume [197:24] and so on. So we are going to use it [197:27] extensively throughout the course, but [197:29] it's good to introduce it right now so [197:31] we are familiar with it. [197:33] So we can do the inspect when it comes [197:36] to containers. You can do it for running [197:37] or for stopped container. So a stopped [197:39] container can be inspected. You're only [197:41] inspecting it. You're not trying to do [197:43] traffic through it or anything else. And [197:45] here's the usage. We can do docker [197:48] inspect and the name of the container. [197:50] Of course, the ID is also or can be done [197:54] docker inspect engine x latest. So, so [197:58] this is for a container and this is for [198:00] the image and you can put the engine x [198:02] latest or a specific version or just [198:04] remove the column and latest and it will [198:06] be understood that this is the latest. [198:08] we'll get information like image ID, [198:10] creation time, and more than that. Okay, [198:13] so let's go ahead and try the Docker [198:15] inspect command. [198:18] So I'm at the Docker host. I'm going to [198:21] connect. I'm going to use EC to connect. [198:23] You know what? Let's let's try session [198:24] manager for a change. [198:27] So let me do this. All right. So session [198:30] manager this time. I'm going to show you [198:33] that they could be either one for as [198:36] long as you are comfortable with one of [198:38] them that's fine. So here's the prompt [198:40] the dollar sign and what we'll do is [198:43] sudo [198:46] su and I'm going to do cd [198:50] and I'm going to go back to the root. [198:52] Now if you do pwd you'll be at the root [198:55] folder and here you can see that we are [198:59] at the root and here's the private IP [199:01] address of the instance. All right and I [199:03] have root privileges. I've elevated my [199:05] privileges. So now I can do any commands [199:07] I would like. Okay. So let's do docker [199:10] ps. I don't have any running containers. [199:12] docker ps minus a. And then now we have [199:16] let me just minimize it a little bit so [199:18] we can [199:20] see the containers. So this is ah it's [199:23] not the perfect output. You know what? [199:25] Let me shift to the other one. This is [199:27] container three and then container two [199:29] and container one. I would rather see it [199:31] on a one line and this is not going to [199:35] help. Maximizing or minimizing is not [199:36] going to help. So let me I'm going to [199:39] leave this for second terminal but I'm [199:42] going to go and do an EC2 instance [199:44] connect one. And I think the output is [199:47] better organized on the EC2 instance [199:50] connect one. [199:56] All right. So, let me do a clear. Let me [199:58] do a sudo su. And if I do pwd, see here [200:03] I am at the /home/obuntu. [200:06] Whereas on the systems manager, I was at [200:09] the root. So, please pay attention to [200:12] the differences if you are if you decide [200:14] to use the session manager instead of [200:16] the EC2 instance connect. All right. [200:18] Okay. So, what do I need to do now? As [200:20] we mentioned docker ps minus a and as [200:24] you can see we have container one [200:26] container 2 container 3 and elastic borg [200:29] and all of them they have exited about [200:31] 20 hours ago. All right. Okay. What do [200:34] you want to do? So we do we want to do [200:36] docker inspect container one for [200:39] example. So we have plenty different [200:43] pages of output. So all of this is the [200:45] output and that's why we said low-level [200:47] details about the container. So this is [200:49] the output of the command when we [200:51] inspect a container. Let's find out few [200:53] fields that are going to be beneficial [200:55] and we're going to look at them later on [200:56] as well. First of all, if you look here, [201:00] we did container one. So this is the ID, [201:02] right? E6 and it it ends with 092. So [201:06] you'll find it here that you have the ID [201:08] the exact same. This and this are [201:12] exactly the same. So that's the ID of [201:14] the container when it was created. So [201:16] that was created close to 20 hours ago [201:19] in and then we have the arguments the [201:23] engine X and if we look here you'll find [201:27] that it is from engine X actually [201:29] status exited [201:33] and the image where it was created from [201:39] and notice now when we're talking about [201:40] resolve conf path host name path any [201:43] path inside the container see where it [201:45] starts [201:47] under the var lib docker. This is where [201:50] the docker will be installed and any [201:52] folders that has to do with docker are [201:54] going to be subd directories from that [201:57] folder or from that path. So here we [202:00] have the containers path for example [202:03] they all start with vl docker vlib [202:06] docker. All right. Name container one. [202:09] Platform is Linux. [202:16] Networks. We're going to look at that. [202:18] And the port bindings if any. We're [202:20] going to look at that later on. But this [202:22] is an important part that we should also [202:23] look at when we are inspecting for [202:25] networking. [202:27] And if we scroll down [202:31] path graph drivers mounts is very [202:34] important. if we have any volumes [202:36] attached to the container [202:41] and the image engine X volumes we don't [202:43] have any volumes attached to it right [202:44] now [202:46] and if we scroll down more network [202:49] settings information about the network [202:52] and the network is a bridge and as we [202:55] scroll down [202:57] oh we don't have any IP address [202:59] assignment right now because it is in [203:01] exited mode [203:04] all right DS DNS name and a lot of other [203:06] things that are important. So let's [203:08] bring this container to life. So let's [203:10] do docker start count one. [203:14] So now it has started. Let me docker ps [203:16] to verify. Yeah, it has started. So let [203:19] me repeat the same command again and see [203:21] the network part. What will be the [203:24] difference? Oh, I'm sorry, not start. [203:25] Inspect. [203:28] Okay, see for the network part you'll [203:31] find now that we have a MAC address, a [203:33] layer 2 network address and then we have [203:35] an IP address on the container and we [203:37] have a gateway for the container which [203:39] was null before. So this is important [203:42] because now we can see that when it is [203:45] active it has networking components. We [203:47] are going to cover a full section on [203:49] networking so don't worry about that. [203:51] All right so that's docker inspect and [203:54] also we can do docker inspect for [203:56] images. So I can do engine X [204:01] and now I'm inspecting an image. So we [204:04] have here type and we have layers in the [204:06] image. We're going to talk about layers [204:08] later on. Let's go up and find from the [204:10] start what information we got. So here [204:12] is where we started. So the ID of the [204:15] image [204:21] configuration host name domain name and [204:23] all that we don't have any information [204:24] about that path [204:27] engine x version [204:31] and the command that executes when the [204:34] container runs is engine x to start [204:37] engine x. Basically we don't have any [204:39] volumes [204:45] and labels. The maintainer of this is [204:48] engineext docker maintainers [204:50] docker-mineext.com [204:54] and the OS is Linux the size [205:02] and that's it and metadata last tag [205:05] time. All right, let's conclude our [205:09] discussion about basic Docker commands [205:11] with Docker RM. If you would like to [205:13] move a container, remove means delete, [205:16] completely move it or remove it from [205:20] your containers on the Docker host. [205:24] Docker RM and the name of the container [205:27] is going to only remove the stop [205:29] containers, [205:31] not the running ones. What if I need to [205:33] remove also the running ones? Then I [205:35] need to have the hyphen f or the -ashf [205:39] which is force the removal or the [205:41] delete. Here's an example. Docker rm. I [205:44] can put the container ID or the [205:45] container name. And I can do multiple [205:49] containers at the same time. And I can [205:51] only add from the ids the first few [205:54] letters if I would like to. [205:57] And minus f is to force stop the running [206:01] containers and then delete it. [206:03] What if I need to remove images? Then I [206:05] have docker rmi remove image. So these [206:09] can remove one or more docker images [206:11] from the local system. But if I have a [206:13] dependent container on one of the [206:15] images, it will not be removed. Again, [206:16] minus f means remove the image. Even if [206:19] there are containers stopped or running [206:21] created from that image. [206:24] Here's an example. Docker RMI my image [206:27] and Docker RMI multiple images and [206:30] Docker RMI minus F remove the image [206:34] force the removal that has dependent [206:37] container created from it. [206:40] All right, the next command is docker [206:41] logs and then we have options and the [206:44] container ID. This is to read logs of a [206:47] container. Basically logs are important [206:50] if you are doing debugging, if you are [206:51] doing tr troubleshooting or we want to [206:53] monitor logs for application or for [206:55] processes running in the container. [206:58] Here's an example. Docker logs my [207:00] container [207:03] and docker logs and follow my container. [207:06] So that means it will display the logs [207:08] and keep updating the terminal the [207:11] output with the logs with the new logs [207:13] not just getting me what is in the [207:15] container and that's it. [207:17] What if I need an option for a docker [207:19] run but I don't remember it. So you can [207:21] do docker hyphen help or you can do [207:24] docker specific command hyphen help. So [207:27] for example docker run double hyphen or [207:30] d-help. [207:32] This will give me the list of available [207:33] option and flags for this command. So I [207:36] can do it with docker commit. I can do [207:38] it with docker inspect and so on. [207:41] Then if I have images that are not used [207:44] and I would like to free up space on the [207:46] docker host then I can do the command [207:48] docker image prune. So this is going to [207:50] remove the images that I'm not using. [207:52] Let's go ahead and do this in the [207:54] hands-on lab. So let's see what images [207:58] and containers we have. Okay minus a. So [208:02] we have container one, two, three and we [208:04] have this random container and they are [208:07] from Ubuntu, EngineX, Python and Bash. [208:10] So what images do we have? [208:13] We have the Ubuntu utilities engine X, [208:18] Python, Ubuntu and Bash. So we have [208:19] these images and we have this. Let's say [208:21] you would like to clear up space on the [208:24] host because there are some images that [208:25] you are not using. So you can easily do [208:28] docker rmi [208:31] and then the name of the image. So if we [208:34] have this python [208:36] unable to remove repository python there [208:39] is a container using it. [208:42] That's why you cannot remove it because [208:43] we have one here that is from python. [208:46] All right. So what do I need to do then? [208:48] Then I can force removal rmi minus f [208:53] and the image name. And now as you can [208:57] see it is removing that. And if I do [208:59] docker docker images [209:03] now python is gone although there is one [209:06] container dependent on it and it's still [209:08] here. Let's do docker rmi remove [209:11] multiple [209:12] in and I I'll do minus f because there [209:16] are containers dependent on them. I'm [209:18] going to remove the bash. I'm going to [209:20] remove the Ubuntu and I'm going to [209:22] remove the engine X [209:25] docker images. I'm going to retain this [209:28] one because as you know that this one is [209:34] having the tools that I usually use. So [209:36] I'm going to keep this one. I'm not [209:37] going to remove. Now let's go ahead and [209:39] check what can we do with the [209:41] containers. [209:43] Docker rm. This is for the container. [209:46] And then I'm going I can do 0cc. So the [209:49] first three letters from this one and [209:52] 5d7 which is the first d three letters [209:56] from the second one. So now I'm removing [209:58] two containers at the same time. Let me [210:00] see what happens. Docker ps minus a and [210:05] we have container two and three. So this [210:07] one and this one are now are removed. [210:10] Okay, let me start one of the stopped [210:13] ones and then I'm going to see what [210:15] happens with the container when it is [210:18] running and I'm trying to [210:21] let me run a container docker run minus [210:25] it. Let's say name is container 5. [210:31] And I'm going to run it from this image, [210:37] the one that is left here. [210:40] and 1.1. So we have to put the tag as [210:44] well because this is what I have here. [210:46] So I'm going to run this one in a bash [210:48] shell. So I have it right here. [210:53] Okay. And I'm going to open a new [210:57] window, new terminal, and I'm going to [211:00] try and remove it. So it is running and [211:03] I'm going to try and remove it and see [211:04] what happens because I want to show you [211:07] that you can do the minus f command or [211:09] the minus f option to the command sudo [211:12] su and then docker ps [211:16] docker ps. [211:19] Okay. So I'm going to do docker rm [211:22] container 5 and let's see what happens. [211:25] So you can't because the container is [211:27] running. So I can either stop it and [211:29] then remove it or I can do docker [211:32] rm minus f container 5 and it's going to [211:35] kill container 5. So docker ps now I [211:39] don't have anyone running docker ps [211:42] minus a and now we have two containers [211:47] running. I can remove them in one shot. [211:49] Now I can do container two, container [211:52] three or I can use the first the the [211:54] container ids or the first few letters [211:56] from each ID. And now we don't have any [211:59] containers left stopped or running. And [212:02] I have only one image left which is the [212:06] one that has the ping and curl and all [212:08] that stuff that we used before. Now [212:10] let's try the docker help. Let's say I [212:12] am stuck with docker run [212:15] or docker commit and I'm not sure what [212:18] options I can use with this command. So [212:20] I can do docker help [212:23] and then it will tell you that you can [212:25] do minus a to add the author minus c to [212:28] apply docker file instructions minus m [212:31] to add a commit message to post [212:34] container during commit. So these are [212:36] the available options and here it gives [212:38] you the syntax. So, docker container [212:40] commit or docker commit and then the [212:42] name of the container here [212:46] and the image that you're going to [212:49] create from it. All right. [212:52] All right. Now, let's move to the next [212:53] one which is the docker logs. [212:59] So, I have a script for you. [213:03] So, we're going to run a container [213:07] with this script. It's a long command [213:09] that's why I'm copying it. So docker run [213:13] itd interactive detached mode name is [213:16] container logs and the image is alpine [213:19] and then it shell it will run a shell [213:21] command [213:23] while true do date it will print the [213:26] date sleep for two seconds until the two [213:29] seconds are done then there will be logs [213:31] in the container [213:34] so alpine doesn't exist it will have to [213:36] download it so for two seconds it will [213:39] be printing the date And now what we [213:42] need to do is I need to do docker logs [213:44] and the name of the container. We have [213:47] to docker ps first. [213:50] So we'll do docker ps [213:52] and I'm going to do docker logs and the [213:57] ID of the container. [214:00] And you'll see now it was printing the [214:02] logs. [214:07] This course would never be possible [214:09] without your support. In order to [214:12] support us develop more free content [214:14] that is high quality at no price to you [214:17] like this one, consider buying the full [214:21] package of this course on www.dined.com. [214:25] It can be found at this address [214:27] www.dlphinet.com/courses/doccker. [214:31] Very easy URL to follow. And for a price [214:35] of a lunch or even less with the [214:37] inflation that we are living in right [214:38] now, you can support us develop more [214:41] free and quality content like this one [214:44] to help you throughout your learning [214:46] journey and to help the masses as well [214:48] across the globe. If you buy the full [214:50] VIP package, as I like to call it, [214:52] you're going to have lifetime access to [214:54] the content and its updates. It's going [214:57] to be split into video lectures. So you [214:59] don't have to be overwhelmed with seven [215:01] or eight hours or even 15 hours a single [215:03] video. You can have that divided into [215:06] separate lectures for theory and [215:08] hands-on. You are going to have access [215:11] to the full 15 hours version of this [215:13] course and you're going also to have [215:15] additional hands-on labs on the topics [215:18] that we have covered but at at a deeper [215:20] level. You'll have a second realworld [215:23] capstone project that will deepen your [215:25] real world experience with Docker and [215:28] also you'll have a community access to [215:30] that community for faster Q&A support [215:34] and of course the ability on our [215:36] platform to have quizzes and assignments [215:38] is going to be there as well. And also [215:41] you'll have access to the scripts for [215:43] all the hands-on labs and the 330 pages [215:46] PDF guide that includes all the slides [215:49] of this course. We appreciate your [215:51] support if you can and that would [215:53] definitely be a good return on [215:55] investment to yourself as well through [215:58] more free content that we can generate [216:00] through your support. [216:08] When using Docker, it is very handy to [216:10] use an IDE, an interactive development [216:14] environment like VS Code. I mean it's up [216:16] to you if you want to use a different [216:17] one but I'm going to show you where you [216:19] download VS Code from from Microsoft. [216:22] It's free and also how to you can [216:24] install the Docker extension is because [216:26] we are going to use it in our [216:27] demonstrations moving forward. So if you [216:30] head to Google and you just type VS code [216:33] download and you'll find the official [216:35] website visualstudio.com download. Click [216:37] on that and then here you'll find out [216:40] the Windows installation and then you'll [216:42] have the Mac installation and if you are [216:44] working on a specific Linux image as [216:46] well. Okay. So if you click on Windows [216:48] for example then you'll find that the a [216:50] direct download link is going to start [216:53] or if it's not started you can click the [216:56] link. So this will download the package [216:58] and then you can just double click it if [217:00] you are on Windows and then you can [217:02] follow the instructions and yes yes yes [217:04] continue and add the user agreement and [217:08] then you'll have the file add the [217:10] shortcut to the desktop and life is [217:11] good. So you have VS code. Now the next [217:15] one is we need to open VS code and we [217:17] need to install the Docker extension. So [217:21] it will help you as you write Docker [217:24] code basically or Docker scripts. So [217:26] let's go ahead and do this. [217:28] So if you are in VS Code, what you need [217:30] to do is you need to click on this which [217:33] is the extensions [217:35] and then here you would like to look for [217:38] Docker [217:41] and this is the one that we are looking [217:44] for edit smarter ship faster and so on. [217:47] In my case this is already installed so [217:49] I can uninstall it and disable it. So [217:51] it's installed and enabled. In your [217:54] case, if you didn't have it before, then [217:55] you will have here install. Click on [217:57] install. It will take some time and it [217:59] will be installed. Make sure that after [218:03] that is done, then here it's going to [218:05] show disable and uninstalled. [218:09] If this is what you can do, that means [218:11] it is installed and enabled. So, if this [218:14] one shows enabled, please click on it. [218:17] If it shows disabled, don't do anything. [218:18] You are good to go. If this one shows [218:21] install, that means you need to click on [218:23] it to install it. If it shows uninstall, [218:25] you're good to go. Don't do anything. [218:27] So, you're looking at that it should be [218:30] exactly like it shows here. And the auto [218:32] update in case if there are any updates, [218:34] you can do that as well. All right. So, [218:36] we need the one from Docker, not from [218:38] Microsoft, not from any other ones, the [218:41] one from Docker. And you need to install [218:43] it [218:45] and make sure that it's enabled. That's [218:47] it for this hands-on. Please install [218:50] Visual Code and please install the [218:53] Docker extension. Let's look now at how [218:56] you yourself can customize a Docker file [218:59] based on what application you are using. [219:01] So for example, you would like to run an [219:04] application that is written in [219:05] JavaScript. Has nothing to do with the [219:09] base images that are available except [219:11] for the fact that you need to run it on [219:13] Ubuntu or Alpine or Fedora or Red Hat [219:16] Enterprise Linux whatever the base image [219:19] is. But then you have a lot of files and [219:22] dependencies and code that you would [219:23] like to upload. So now you are [219:25] customizing an image. How can you write [219:28] the text file which is the docker file [219:31] from which you can use the docker build [219:33] command to build an image and then you [219:35] can use that image for creating your [219:38] production of course de development [219:40] testing and production environment [219:42] eventually [219:43] and also using the same technique [219:46] whenever there is an update to the code [219:48] or update to the dependencies or the [219:50] runtime version that you would like to [219:52] use you can go back into your docker [219:55] file create a new version. So now you [219:57] are maintaining that let's say in GitHub [219:59] in a repository version two and then [220:02] update whatever you like create from [220:04] version two image two and then from that [220:08] you can build also new containers and [220:10] then you can decide on how the migration [220:12] will happen. So the essence is building [220:15] and customizing your docker file from [220:18] which everything else happens and this [220:20] is what we're going to discuss right [220:22] now. [220:24] A docker file is nothing more than a [220:26] text document and in that text document [220:29] you tell the docker engine all the [220:31] commands that a user would have [220:34] otherwise done manually on the command [220:37] line to build the application. So what [220:40] we are trying to say here is the [220:43] instructions in the docker file are [220:45] nothing more than the actual commands [220:47] that you would have used manually on the [220:49] CLI to build your application. So if I [220:52] wasn't going to use containers and I [220:54] wanted to build the same application [220:57] using command line, I would have done [220:59] that step by step manually in the [221:02] command line. Let's say start a virtual [221:04] machine Ubuntu virtual machine and then [221:06] go into the console and start as the [221:08] root user or as a privileged user to do [221:12] make directory cd copy run apt update [221:16] yum install and all that stuff. That's [221:18] exactly what we do. But we would like [221:20] that to be automated and that's why we [221:22] build the docker files. So how would a [221:24] simple docker file look like? This is an [221:26] example where we are instructing docker [221:29] please build an image that is going to [221:32] download the base image from Ubuntu. And [221:34] I could of course include colon and then [221:37] a specific tag for a version if I wanted [221:39] to who created this docker file and that [221:43] will be in the image as well the details [221:45] of who created that the author [221:47] basically. And then I want to execute [221:50] the command apt apt get update. So I [221:54] want to run this command. And then at [221:56] the end please execute this command. [221:59] Echo hello from dolphin ad. So that's a [222:01] very basic and simple docker file. But [222:05] as you can see it's all text. You can [222:07] write it in your preferred editor or [222:09] maybe in VS code or any other IDE in [222:12] order to give you help with the Docker [222:13] plugins and all that. And you can build [222:16] it and life is good. Very easy. And from [222:18] that you are going to save it as a [222:21] Docker file and then you execute it with [222:22] a Docker build and boom you have an [222:25] image. Docker can build these images [222:28] automatically by reading the [222:30] instructions from a Docker file. [222:35] And how does that happen? When we have [222:37] the Docker file edited and saved, then [222:40] we can use the Docker build command. And [222:43] in the docker build command instruct it [222:45] or let it know where is the docker file. [222:48] So it will read the instructions and it [222:50] will create a docker image. That's how [222:52] simple the whole process is. So let's [222:55] understand the syntax. I mean we have [222:57] here from all all uppercase maintainer [222:59] all uppercase run all uppercase cmd all [223:01] uppercase. What does each one of these [223:04] mean and also what are the other options [223:06] that we could use. So let's go ahead and [223:08] start to investigate that. So let's [223:10] start with the very first one. The [223:12] docker command or the docker file [223:14] instruction from [223:16] the from is nothing more than letting [223:20] docker [223:21] get the base image on top of which the [223:24] image is going to be built. So the [223:26] syntax is from and then the name of the [223:28] image and the tag or the version in case [223:32] there is a version to be followed. Let's [223:34] say I have after that run I have command [223:37] and I have other instructions. So all [223:39] these instructions will be based on the [223:41] image that we have downloaded or created [223:44] a layer for in the image based on the [223:47] from instruction. [223:49] So this one for example from Ubuntu [223:51] means since there is no colon and tag [223:55] that means please pull the latest B [223:57] Ubuntu image and the following [224:00] instructions are going to be based on [224:01] Ubuntu. [224:05] When you have a Docker file that has [224:07] multiple instructions, when an image is [224:10] built, [224:12] Docker is going to build each line in [224:14] the Docker file, each instruction in the [224:16] Docker file as a separate layer in the [224:19] resulting image. So for example, here if [224:22] we have a Docker image that has four [224:24] layers, this could be corresponding to [224:26] the file that we had. So the from is [224:29] going to map to a layer. The maintainer [224:31] is going to map to a layer. The run will [224:33] map to a layer and the command will map [224:35] to the layer. Why is that? Why is it [224:37] built in this structure? And that's a [224:40] long story about the union file system [224:42] that the docker images use. But the [224:44] point simply is if you have these [224:48] segregated from each other then if you [224:51] want to build a derivative from this [224:53] image let's say I go later on and then I [224:56] change the author and this will be John [224:58] Doe plus George Watson. [225:01] So now it will update the corresponding [225:04] layer only without having to impact or [225:08] download or change the other layers. So [225:10] the new image will will reuse the [225:13] existing layers but will only change the [225:15] one for which a change has happened in [225:17] the docker file. So that's the simplest [225:20] the layman terms of why it is layered [225:22] and we're going to play with the layers [225:25] also in the hands-on labs. [225:29] Second instruction we need to look at is [225:31] the run. So remember from B image now if [225:35] you have any run commands they will be [225:37] run based on that B image. So run will [225:42] run one or more commands normal commands [225:45] that you would have otherwise done [225:47] manually. [225:48] So the run instruction will execute any [225:50] commands in a new image layer and commit [225:53] the results and the syntax is run and [225:56] then you put the command or commands [225:58] there could be multiple commands not [226:00] only one. So here's an example I have a [226:03] statement in my docker file. So let's [226:05] say we started with from Ubuntu as we [226:08] did in the previous one then run apt get [226:11] update. So this command is based on the [226:14] fact that we are starting with Ubuntu. [226:16] If it was Alpine, maybe it was going to [226:18] be apt with a K, not apt. If it was Red [226:22] Hat Enterprise Linux or Rocky Linux, for [226:24] example, this would have been yum. So, [226:26] it all depends on which base image and [226:28] then what will be the commands that you [226:30] would have used manually on that base [226:33] image or operating system if you will. [226:35] So run apt get update and then run apt [226:38] get install and yes for any questions [226:42] vim and I can do also get I can do echo [226:45] I can do nano and other tools that I [226:48] might need to use as well. So these are [226:50] two instructions and they will end up [226:52] being two different layers in the [226:54] resulting image. [226:59] All right. Is there a way I can minimize [227:02] the number of layers by combining run [227:06] commands? And the answer is absolutely. [227:08] This is actually not the recommended way [227:10] because now you are creating multiple [227:13] layers for no reason. And the [227:15] recommended way would be that you can [227:17] combine both. So you can have the two [227:20] amperands which means do this command [227:23] and this command to install them and [227:25] this command to install get and you can [227:27] have more than one. So all of these is [227:30] going to translate into one layer in the [227:32] resulting image. [227:35] So fewer image layers. One might ask but [227:38] is it a rule that we try to minimize the [227:41] layers as much as we can? This is all [227:44] based on what is it that you are doing. [227:46] So if you want to run different packages [227:49] and you know that down the road one of [227:51] them is going to be changing frequently [227:53] which will result in that this layer [227:56] will have to be run again and again and [227:58] executed in every update then maybe you [228:01] would think no no no I don't want to do [228:02] that uh for Vim I don't want it to be [228:05] updated regularly so I'm going to [228:07] separate it in a separate run command [228:10] and the others I'm going to combine [228:11] them. So minimizing the layers is [228:15] sometimes a very good idea and sometimes [228:18] it is required to have multiple and [228:20] separate layers depending on the [228:21] frequency of the updates. The docker [228:24] history command can help you find out [228:27] what are the layers in the base image if [228:29] you will or in the resulting image that [228:31] you have created and you can use it to [228:33] inspect the layers available or the [228:35] layer details in any image. very handy [228:38] to use when you would like to find out [228:41] what is the number of layers available [228:43] and what do they map to exactly in the [228:45] instructions in the docker file. So very [228:47] easy docker history and the name of the [228:49] image that you are using that you have [228:52] on the local host and it will tell you [228:53] everything about it. Still with docker [228:55] files let's look at the cmd or the [228:58] command instruction in a docker file and [229:00] also how we can build images using the [229:03] docker build command the command or cmd. [229:06] So this is to specify the command to be [229:09] executed when the container is started. [229:11] If you think about it run that was maybe [229:14] installing uh something updating [229:16] something that is run command when the [229:19] container runs what is the command that [229:21] will be started is it bin bash shell [229:24] terminal is it going to run engine x is [229:26] it going to do an echo command that's [229:28] what we mean by to be executed when the [229:30] container starts and the syntax is we [229:33] have command and then I mean this is the [229:36] JSON and the preferred way then we have [229:39] the brackets the square brackets and [229:41] Then what is the command? So this could [229:43] be echo for example, can be ls, can be [229:45] something else and then parameter 1, [229:47] parameter 2 and so on. [229:50] Usually only one command instruction [229:53] should exist in a docker file. But what [229:55] if I am building this image from an [229:59] image that already has a command and I [230:00] would like to add a command in my file. [230:02] What happens? If you have multiple ones, [230:04] then the latest one is going to be the [230:07] one that will be executed. So only one [230:09] will be executed. The weak side of the [230:13] command is that it can be overridden at [230:15] container start time. Don't rush it. I'm [230:18] going to show you that in the hands-on [230:21] maps. Here's one example. Command square [230:24] brackets. And then we have the double [230:27] quotes echo. So this is the command to [230:30] be executed. And here is the message [230:32] that will be echoed. So this is the [230:34] parameter for the command. And the [230:36] output after the container runs will be [230:38] hello from dolphinet. That's it. [230:42] And if we have another example, if this [230:44] is the command that will be executed [230:46] when the resulting image from this [230:49] docker file is going to execute when we [230:52] run a new container. So that will be the [230:54] command to be executed when a container [230:56] from the image is created at the start [230:59] time. And this will execute Python [231:01] command and the argument. Okay, Python [231:04] will run to do what? To run the app.py [231:07] the code that is in this file. So this [231:10] will run Python app. py at the container [231:14] start time. [231:16] Now let's contrast command and run. We [231:19] don't want to leave any confusion. So [231:21] run is going to execute at the build [231:24] time when the image is being built. That [231:26] is called the build time. When we are [231:29] creating a container from the image, [231:31] this is called the runtime. So we have [231:33] to separate the two. Building the image [231:34] from the docker file is build time. [231:37] Creating a container from the image is [231:40] runtime. [231:42] So at build time if you want to execute [231:45] commands update, yum install and so on. [231:48] This is the run command and what it is [231:51] used for and it will add layers to the [231:53] images and it is used to install apps [231:56] and tools and so on. [231:58] executed at runtime is the command. So [232:01] when we start the container, this is [232:03] where the statement is effective and it [232:05] runs a command at the container when it [232:08] is started. /bin/bash echo lsc cat [232:12] whatever that is. Now we have already [232:16] built our docker file and now we would [232:18] like to translate that into an image. [232:20] What do we do? So you can use the docker [232:23] build command and you can pass options [232:26] to it and the path the path is the build [232:31] context which is the files you need. You [232:33] want to copy these files into the [232:34] container. You would like to move the [232:35] app. py into the container because it [232:37] will be executed. So this is called the [232:40] build context and the build context area [232:42] is usually protected by docker. [232:46] So for example, if I do docker build [232:49] minus t. So that's part of the options. [232:51] Minus T means tag. Provide the image [232:54] this tag or this name. And you could [232:56] have versions as well if you wanted [232:57] colon and 1.0, 1.2, 1.3 and so on. And [233:01] the dot here means that the current [233:04] directory on the local host is where all [233:07] the files and all the build documents or [233:11] data that you need in order to execute [233:13] the docker file. All right. So where is [233:17] the name of the docker file? You don't [233:18] have to specify it if the default name [233:21] is used which is docker file one word [233:24] with a d in uppercase [233:30] and the options as we mentioned flags [233:31] you can pass to customize the build. So [233:33] minus d is one of the options that we [233:34] have used and then by default docker [233:37] looks for a file named docker file. What [233:40] if the d was a lower case? It may work [233:44] but it is looking for a file with no [233:46] extensions and it is one word docker [233:48] file with a capital D. [233:51] Okay. Can we specify a different name? [233:53] Of course you can and that is easy to do [233:56] as well and we're going to look at it [233:57] right now. So let's say if the path as [234:01] we mentioned is the build context and [234:02] usually the current directory. What if [234:04] it is in a different directory? What if [234:06] on the local host I have copied [234:08] everything under a different directory? [234:10] everything in terms of the app. py if [234:13] it's a python application any [234:15] requirements any configuration details [234:18] any path any dependencies [234:21] I have put them in a folder specific to [234:24] that application I am and it is not my [234:26] current directory on the local host how [234:28] do I refer to that that's one thing the [234:31] second thing is what if I'm using a file [234:33] with a different name I I mean I have [234:35] lots of applications and it doesn't make [234:37] any sense that I'm going to call them [234:38] all docker file I want to call it app [234:41] one for the first look file app2.ext [234:44] text for the second app xyz doty yamel [234:49] if I'm in that situation which is very [234:52] logical what can I do so here is one [234:54] example if we have a docker file with [234:58] the name test [235:01] and it is available in a child directory [235:03] from the current working directory [235:05] called files [235:07] and the build context everything that [235:09] has to do with the build the app py the [235:13] code and so on is going to be in a also [235:16] a child directory under the working [235:18] directory called image files. Then this [235:21] is now different because the minus f is [235:24] going to tell docker and by the way when [235:27] you build your file that you should be [235:29] looking at is a subdirectory under the [235:31] current directory and the file name is [235:34] test.ext [235:35] and minus t that's another option. [235:37] Please tag the resulting image with this [235:39] name and you can have the version if you [235:41] want it. And oh by the way when you need [235:43] any files that are going to be copied [235:46] and so on into the container you will [235:48] find these data that is under the [235:51] subdirectory under the current directory [235:53] called image files. So that's how easy [235:56] we can interpret this. [235:59] And here is a more complicated one [236:01] because in the path here I can use [236:04] relative and I can use absolute. So here [236:07] is one with the absolute uh details [236:10] docker build minus f. So this is the [236:13] file I want but the file is under home [236:15] Ubuntu. That's the home user directory [236:18] under apps subdirectory under image [236:20] files and test.ext. That's where it [236:23] exists. And that's the docker file you [236:26] should be looking for. And then please [236:28] tag it with this image name. And by the [236:31] way, the build context where you'll find [236:33] all the documents that needs to be [236:34] copied is going to be under home Ubuntu. [236:36] That's the home user directory under [236:39] build under context files. These are the [236:41] subdirectories nested and then a [236:44] directory called app one. So you can [236:46] have all the flexibility in specifying [236:48] where is your docker file and where is [236:51] your build context because you need to [236:54] structure your file system. It cannot be [236:55] a mess and you cannot put all the files [236:58] for all the applications and then in one [237:01] directory as the build context and you [237:03] cannot name all the files as docker file [237:06] because one will override the other and [237:08] eventually you're going to lose your [237:10] data. So I have my docker host. I'm [237:13] going to connect to it and I'm going to [237:15] start a terminal [237:18] and it's always handy to start a second [237:20] terminal that we might need throughout [237:23] the labs as well. So I'll have both of [237:24] them ready [237:26] and in both of them what I will do is [237:28] I'm going to type the sudo [237:31] su and I'm gonna do a clear and I'm [237:34] ready to go. And of course you know that [237:36] we are working on the home Ubuntu [237:39] directory. [237:41] Same thing here. So do su and clear and [237:44] we're good to go. All right. So we have [237:46] the instructions that we are going to [237:47] use and again it's available to you as [237:50] part of the script. [237:53] All right. So here is what we are going [237:54] to use. Let me minimize this so we can [237:57] focus on the screen. So this will be the [238:00] demo for the Docker file. We'll start [238:01] with a very simple Docker file. So I'm [238:04] going to follow the instructions in the [238:05] file with you. You can follow along with [238:09] me and then you can do the instructions [238:11] yourself. Okay. So I'm going to remove [238:12] this so you can see everything I'm [238:14] doing. All right. Right. So here I am in [238:17] the AWS console and I am on the docker [238:20] host and I have done the sudo su and I'm [238:23] with the root privileges now and I have [238:25] another terminal that is exactly the [238:27] same. So what do we need to do? First [238:29] thing let's make sure that we don't have [238:31] anything on this directory clean [238:32] directory and let's do docker images and [238:36] we'll see that we don't have any images [238:39] except the one that I created long time [238:40] ago. And if we do docker ps minus a, I [238:44] don't have any containers running or [238:46] stopped. So what do we need to do? I [238:48] need to nano or vim a docker file. And [238:52] here is the name capital d docker file. [238:56] So what do you need to do here? I'm [238:58] going to start from an alpine very light [239:01] base image. And what I will do is I'm [239:04] going to use the command or this is the [239:07] command that will execute when the [239:09] container is created and it runs. It [239:12] will be the echo command and the [239:14] argument that I'm going to provide is [239:16] welcome and another argument [239:19] hello [239:20] from dolphin ad academy and we close [239:25] this and we are done. So, Ctrl X, this [239:29] is for nano. Press Y and hit enter. And [239:32] if we would like to make sure that we [239:34] got it right, then I'm going to cat the [239:37] content of the file. And as you can see, [239:41] here we go. From Alpine echo this. So, [239:44] let's build the image. Docker build. Tag [239:47] it with the name [239:49] image one. [239:52] And the building context is the current [239:54] directory. There are no files to copy or [239:56] anything. So it doesn't matter. I'm [239:57] going to do it the current directory. So [239:59] now you can see that it has done it very [240:01] quickly because we have a very small [240:04] command. Basically there is nothing to [240:06] download. There is nothing to update. [240:07] There is nothing to take time. That's [240:08] why it finished very quickly. [240:12] And what we'll do now is I want to do [240:13] docker images to make sure that it has [240:15] been created. [240:18] And you'll find that image one is [240:19] created. And the size is very small [240:21] because Alpine is very small. [240:25] clear and then what we can do now is we [240:28] can do docker [240:30] history I'm going to start with the [240:32] alpine I would like to see the layers in [240:35] the alpine the base image we have used [240:38] okay so we don't have it locally so what [240:40] I will do is I'm going to pull it alpine [240:44] because we need to look at the original [240:47] content or layers and then I'm going to [240:50] compare it to the new one to the one [240:52] that we created [240:53] So I'm going to do docker history alpine [240:55] now. And as it shows here there is one [240:59] layer [241:01] two months ago and it's an add [241:03] instruction in the docker file and it is [241:06] alpine mini roots fs and at the end it [241:09] is compressed. We're going to talk about [241:11] the ad later on. Briefly the ad [241:13] instruction what it does is it's going [241:15] to copy the content and will decompress [241:17] it. So it will unzip it basically untar [241:20] the file. And then we have the layer [241:22] which is the command bin bash. So Alpine [241:25] in itself if I run a container straight [241:27] from the alpine image it's going to run [241:29] the bin bash I'm sorry the bin shell not [241:32] the bin bash the bin shell command. And [241:34] here we have image metadata but here we [241:38] don't have it and that's because it's [241:39] downloaded. It's very common when you [241:41] download an image and you do docker [241:43] history that there will be missing [241:44] lines. missing it doesn't mean the [241:46] content is missing. And the proof is [241:48] here is a size but the metadata is [241:51] missing. That's that's what's missing [241:52] now. Okay. So these are the layers we [241:55] have in the original alpine that I [241:58] pulled the latest one. So now let's do [242:00] docker history but for the image we have [242:03] created image one you'll find the [242:06] original ones the original two layers [242:08] and as you can see now two layers are [242:10] missing the information the metadata [242:13] basically and then we have a new one [242:15] which is the echo welcome from dolphin [242:16] ad. So this is what we have now. So if [242:19] we build a container let me clear if I [242:22] build a container. So, docker run and [242:25] I'm going to create it straight from [242:27] image one without name without anything. [242:30] What do you expect to see? Welcome. [242:32] Hello from Dolphinet Academy which was [242:35] exactly the content of the docker file. [242:38] If we c it again docker file. [242:43] So the echo command was executed and [242:45] then it appended this as an argument and [242:47] this as an argument and that's where we [242:49] ended or how we ended with welcome hello [242:51] from academy. All right. So this is our [242:54] first file that we have and I can do [242:57] docker ps minus a. We don't need this [243:00] container anymore. So I can do docker rm [243:03] and then b a5 the first three letter [243:06] from the id ba5 and it's going to remove [243:09] it. [243:11] If I repeat the command now it won't [243:13] have anything running or uh exited. All [243:16] right. So let's create another docker [243:19] file. So let me remove the docker file [243:22] that we have or you can edit it. It's up [243:24] to you. I can delete this or I can edit [243:26] it if you want. Let's go ahead and edit [243:27] it. Maybe it's a better idea. So nano [243:30] docker file. So we have our file in [243:34] nano. If you would like to delete a [243:36] line, you do ct controll ktrl [243:40] k again. The file name is still docker [243:42] file. As you can see the file still [243:44] exists but now it's empty. So what we [243:47] are going to do now? I'm going to create [243:49] another image. You have it in the script [243:51] from Ubuntu. [243:54] Of course, you can go and do 2204 for [243:57] example, if you would like to if you [243:59] have a specific version because before [244:01] we did from Alpine without any versions, [244:03] it brought in the latest. So, let's do [244:05] this one. And what I will do is I'm [244:07] going to run because it is Ubuntu. [244:11] I'm going to do apt get update. And then [244:15] I'm going to do another run at get [244:18] install minus y and I'm going to install [244:22] them [244:24] and run again [244:28] apt [244:30] get install minus y and we can download [244:35] git for example and at the end I'm going [244:37] to add a command and the command would [244:39] be simply again echo [244:44] And the argument is going to be [244:47] this is an Ubuntu [244:51] image with Vim and get installed [245:00] or we can state Ubuntu container because [245:03] we will see the message when we get the [245:05] container. [245:06] Doesn't matter what you want to write. I [245:08] just want to make it relevant. That's [245:10] it. Crl + X and I'm going to save the [245:13] modifications. Hit enter. And if you [245:15] would like to check the file, docker [245:17] file [245:20] and it is from Ubuntu. App get update up [245:22] get install up get install and echo. All [245:25] right. I don't have [245:28] the Ubuntu image 2204 as you can see. So [245:32] what we'll do is beforehand let me clear [245:34] and let me docker pull and I'm going to [245:38] get the same Ubuntu [245:41] and 220 [245:43] or [245:46] so now it's pulling it. [245:49] Let me just make sure that we got the [245:52] right one. [245:54] CD docker file 2204 and we downloaded [245:57] 2204. Yeah. So we are right. docker [246:00] build [246:02] minus t. So I need to build a new image. [246:04] Let's call it image 2. And this is again [246:07] from a file that is on the local [246:10] directories. That's why I did not add [246:12] here anything about minus a for file [246:13] name. And the building context there are [246:15] no files to copy or anything. So [246:17] everything is going to be on the same [246:20] directory and hit enter. Now you can see [246:22] that there are a lot of steps. So here [246:25] is run apt get update run apt get [246:28] install minus y vim. Once this is [246:31] finished it's going to become run get [246:34] apt install minus y get [246:38] and then the command of course is going [246:40] to be added but it will will not see [246:43] anything here. When we run the [246:44] container, we're going to see the impact [246:46] of the command [246:51] exporting to image exporting layers. As [246:54] you can see, so layers have been created [246:56] and they are being exported. And here [246:58] you can see the steps. So step number [247:00] one, [247:01] step number two, step number three, step [247:04] number four. What you don't see is step [247:06] number five. Okay. So let's do docker [247:09] history. And now I want to see the [247:11] layers in image two. Let's see what we [247:14] we have here. So we have the command [247:17] echo. This is an Ubuntu container with [247:19] whatever run apt get install run apt get [247:23] install them run update and then the bin [247:28] the bin shell. So these ones are not in [247:30] my file. Where did they come from? So we [247:34] have the command and we have the three [247:35] runs and it was from Exactly. It was [247:38] from Ubuntu. So these ones must be [247:40] coming from Ubuntu. Also if you notice [247:43] here there is a command that was already [247:46] in whatever that has to do with these [247:48] layers. So what we need to do is I can [247:50] do docker history and then Ubuntu 22.04. [247:57] Let's compare this here to these lines [248:02] here. So the count is 1 2 3 4 5 6 and [248:07] the count here is 1 2 3 4 5 6 and they [248:10] are exactly identical and it ends with [248:14] the bin bash and we have the label orgo [248:16] open label or open arg launchpad build [248:21] and arg release. So the layers from the [248:24] original base image plus the layers from [248:28] my file are both added as if the from [248:32] Ubuntu has added these layers because [248:35] it's bringing them from Ubuntu and then [248:38] the the other instructions in the file [248:40] have built the other four layers. All [248:42] right. So let me clear it and let me do [248:46] a docker run- [248:50] it and I'm going to build a container [248:53] and this will be from image 2 and I [248:56] would like to execute the bin bash. So I [249:00] want basically to get into the container [249:02] I would like to make sure that vim is [249:03] present and also get is present. [249:08] So now if we do on the other terminal [249:10] just to make sure that this container is [249:12] running docker ps I have a container [249:15] running 8 seconds ago created from image [249:17] 2 and it is running bin bash and if I [249:21] get here and I want to in to try vim [249:25] abc.ext [249:27] so it works [249:29] it somehow [249:31] halted. So what I will do is I'm going [249:33] to docker ps minus a. So we have it [249:37] running. I'm going to stop it. And the [249:39] ID of the container [249:41] for some reason them [249:44] has stopped. [249:47] So now it's stopping the container. [249:51] All right. So if I do docker ps minus a [249:53] again, the container has stopped. Now [249:58] let me get into the container again. [250:00] docker start and the name of the [250:03] container or the ID. [250:06] So I'm going to start it and then now I [250:08] can do docker exit minus it [250:12] and again the container. [250:15] Oh, I I didn't put the command. So I'm [250:18] going to do bash. [250:20] Now I'm inside the container again. All [250:22] right. And I want to check if I have get [250:25] hyphen version and I have get installed [250:29] already. And if I want to check them [250:32] without having to get into it again, I [250:33] can do which vim. And then it shows me [250:36] that is installed. So this is what we [250:40] have seen based on the image that we [250:42] have created. [250:49] Still with docker files. Let's now have [250:51] a look at the expose and copy [250:54] instructions or docker file commands [250:56] that we can use. Let's start with the [250:59] expose one. So the expose only informs [251:03] docker that the container is supposed to [251:05] or listens on the port at runtime. So it [251:10] is expose and then the port or it can be [251:12] multiple ports. And here's an example [251:15] expose 80. That means the docker file [251:18] informs docker that the container we are [251:22] talking about in this docker file is [251:24] exposing or supposed to listen at port [251:27] 80. And if we do expose 80443 [251:31] and if we do at space 443 that means two [251:35] ports the container will listen on two [251:36] ports 80 and 443 for example. Okay. Now [251:40] what's the reality of exposing? Does it [251:43] really expose? like does it do the [251:45] mapping and publishing and the linking [251:48] between the container port and the host [251:50] port and the answer is no it doesn't. [251:54] So the expose isformational only if you [251:57] are running manually and building images [251:59] manually and all that it's not going to [252:02] do the publishing of the port or link [252:04] the host to the container. So it does [252:06] not actually publish or expose the port [252:09] open to the host. So you have to do that [252:12] with the docker run hyphen p or hyphen [252:15] publish that we have discussed before. [252:17] However, for tools that autogenerate [252:20] configurations like docker compose like [252:23] docker swarm and kubernetus these tools [252:27] they can do the required configuration [252:30] based on the exposed instruction in the [252:32] docker file. So it is useful to do [252:35] anyways if you are using these tools. If [252:38] not, at least it isformational. Anybody [252:41] looking at the Docker file will find out [252:44] what is the port to expose and maybe [252:45] they will use the hyphen P and then the [252:48] mapping between the host port and the [252:50] container port. [252:53] The second instruction we're going to [252:55] look at what if I need to copy the code [252:58] of the Python application I'm working on [253:00] inside the container when it runs. So it [253:03] will be available inside the image and [253:05] then when I create the container it will [253:07] be available. What if I have any [253:08] dependencies any requirements any [253:10] environment [253:12] data that I need to pass anything else [253:15] that the container needs to run. So one [253:18] way to do that is to use the copy [253:20] instruction. So it will copy new files [253:22] or directories from a source which is on [253:26] the docker host to a destination that [253:29] will be in the image and eventually in [253:31] the container file system at the path [253:34] specified as destination. The copy [253:37] command can only copy files or [253:39] directories from the build context which [253:42] is protected by docker and not from the [253:45] outside. So you cannot download it from [253:46] a storage somewhere in AWS for example [253:50] using the copy command. [253:53] Let's take an example to understand. [253:55] Let's say on the docker host you have [253:58] this project structure. So on the [254:01] current directory you are at right now [254:03] let's say it is the /home/obuntu [254:06] for example. [254:08] Then you have created a docker file. It [254:11] is straight under the same directory [254:14] that you are at right now. Then you have [254:17] created a folder called app [254:20] and under the folder app which is under [254:23] the current directory you have a file [254:26] called main. py. So that could be the [254:30] application Python code and under the [254:34] app directory you have created another [254:36] subdirectory called utils and under [254:40] utils you have a file called helper py. [254:44] So this is the structure of the project [254:46] that you have on your docker host not in [254:49] the container not in the image. So we [254:52] haven't used the docker file to build [254:54] the image yet. We need now to put the [254:57] copy command inside the docker file to [255:00] reference what is in the build context [255:03] and then decide where it will end up in [255:06] the docker image and eventually in the [255:08] container file system. So how would we [255:11] do that? Let's look at the example. [255:14] So we have this example. I mean this is [255:16] a snippet of a docker file. So we could [255:19] have any instructions or commands from [255:22] and run run run run and and that stuff. [255:24] So we're going to copy from app utils [255:29] and I don't have any file name here. So [255:31] I have this is a relative path. So from [255:35] the current directory there is a folder [255:36] called app and yes there is one and [255:40] underneath that there is a folder called [255:42] utils and yes there is one. So I'm going [255:45] to copy this directory with its contents [255:49] completely. I'm going to copy it in the [255:52] image and in the file sim. So this is [255:54] the destination and this is the source. [255:58] So I'm going to take it from here all [255:59] the content of the utilities directory. [256:02] I'm going to copy it in the image file [256:05] system in the container file system [256:07] under / app/code/utils. [256:12] So if these are not existing it will be [256:14] they will be created in the image a / [256:16] app/codes. [256:19] All right. So that's the first one. So [256:21] the app utils directory is going to be [256:23] copied under app code utils inside the [256:26] image and I could have more snippets and [256:29] then I decide to copy the main [256:31] application. So now I do a copy [256:34] from where I am right now. There is a [256:37] sub directory or a directory called app [256:40] and underneath there is a file called [256:42] main. py. So this one is going to take [256:45] all the content in the utils directory [256:48] whether it is one file as we see here or [256:50] multiple files. But in this one I'm only [256:53] copying the main py and I'm going to [256:56] take it to the slash app/code in the [256:59] image. So not / appcode utils that's a [257:02] different path [257:04] one step higher or the parent of the [257:07] utils child directory. [257:10] Why did I do them in two separate [257:13] commands? I could have just copied [257:14] everything local and throw it in the [257:16] file system. This is where we get back [257:19] to the layers that we are talking about. [257:21] When you segregate that then actually if [257:25] there is any change at any point in time [257:27] in the future in the code only [257:30] then only this layer is going to be [257:32] impacted or this instruction because the [257:34] rest is going to be as is. So it is [257:36] cached no changes nothing will be [257:38] touched but this one will be the one [257:41] that will be updated in the image. So [257:42] the caching and speeding up the image [257:45] creation by using cached data that did [257:48] not change in the new docker files. [257:51] All right so hopefully this is clear and [257:53] it clarifies how the copy works and [257:55] please note that it cannot copy files [257:58] from anywhere. It will be from within [257:59] the build context anywhere within the [258:02] build context but not anywhere else [258:04] outside. Let's do a quick hands-on lab [258:07] on expose and copy instructions to [258:09] understand how they work and their [258:11] impact in a docker file. All right. So [258:14] here I am and I have the two terminals [258:16] open. What I will do now is let's do ls. [258:18] So I don't have any docker files or [258:20] anything. So let's create a docker file [258:23] and we want to demonstrate how expose [258:26] works. So nano docker file and I'm going [258:28] to do from engine x [258:32] and expose [258:34] 80. That's it. So that's all I'm going [258:36] to do in the file. Ctrl X. Yes. And [258:40] enter. Now let's build the image. Build [258:45] minus t. Let's call it image [258:48] expose. [258:50] And the build context is going to be the [258:53] local one. [258:54] All right. So I have this [258:58] built. And now if we do docker images, [259:02] I'm going to find one here called image [259:05] exp which is right here. Image exp. [259:09] Let me copy that because we are going to [259:11] use it. And now let's build a container [259:14] from that. So docker run [259:17] image exp. [259:21] So now we have engine x running. I can [259:25] double check from here. docker ps and I [259:28] have one running from this image image [259:31] mgxp 7 seconds ago. All right. So what [259:34] do I need to do? First of all, if you [259:35] look here, there is no mapping at all [259:37] for the ports. There is no publishing [259:39] for the ports. Yeah, but how can we [259:41] guarantee? That's fine. Let's go ahead [259:43] and do one thing. So here is the public [259:46] IP address that I have. Or you can go in [259:50] here and you can copy it from here, [259:53] whichever you like. Let me open a new [259:55] browser. [259:56] And I'm going, of course, by default [259:58] it's HTTP, but I want to write it so you [260:00] can see it. And I'm going to try an [260:03] access on port 80. [260:07] Can't access it. So, how about if I try [260:09] it from the command line? If I do curl [260:17] and then I'm going to HTTP into the [260:21] private IP address of the host. [260:27] And that would be on port [260:29] 80. [260:31] And if you don't have it here, if you [260:33] are not using the EC2 instance connect [260:35] or you closed this before, then you can [260:38] also get the private IP address from [260:40] here. Can just click on these squares [260:42] and you will copy it. And if I try this, [260:45] I'm getting an error as well. So as if [260:49] that the expose in the docker file was [260:53] onlyformational and we did the docker [260:55] build manually. So we are not docker [260:57] compose we haven't used docker swarm [260:58] it's not kubernetus. So they did not [261:01] look and generate the required [261:02] configuration for that to work. So looks [261:05] like it's a failure and we couldn't get [261:07] access. So let me stop this container [261:10] and do I'm going to do ctrl c. [261:13] Now if we do docker ps I shouldn't find [261:16] any active. Let's do a clear. And what I [261:20] will do now is I'm going to do docker [261:21] run. I'm going to do minus p. And I'm [261:24] going to map port 80 on the host to port [261:26] 80 on the container. [261:29] And this is going to be from image [261:33] I think if I'm not mistaken it was image [261:35] exp. [261:37] All right. So I'm going now to map port [261:40] 80 on the host to port 80 on the [261:42] container. And this is the image we are [261:44] creating this container from. [261:48] If I hit enter, I have now [261:52] engine x container running. If I move to [261:54] the other container and if I do here [261:58] from the other terminal, we are going to [262:00] check docker ps. And yes, I have one [262:03] running and it's up. And you can see [262:05] here the difference. So the previous [262:07] container when you look at the ports [262:10] they were just talking about the port [262:11] that the container is listening on but [262:14] here you can see that there is a mapping [262:17] from the local host on port 80 to port [262:20] 80 on the container and this is for IPv4 [262:23] and this is for IPv6. [262:26] So no matter how you will come into the [262:29] container on into the docker host using [262:32] port 80 you should be able to make it [262:34] into the container. Let's check. Let me [262:37] refresh this. And here you go. Welcome [262:40] to engine X. So now you can see that [262:43] expose in the docker file is [262:44] onlyformational. [262:47] And you have to do the publishing [262:48] yourself or you have to use a tool that [262:50] will get that piece of information from [262:52] the docker file and then do the required [262:55] configuration when it is creating the [262:57] containers in order to expose or publish [262:59] the port between the container to be [263:02] mapped to a host port. All right. So I [263:04] think that is clear. So let's do a Ctrl [263:07] C. [263:09] And here I'm going to do a clear and [263:12] let's move into the copy part of what we [263:15] need to do. Okay. So let's create a file [263:17] called test.ext. [263:21] Hi. This is testing the copy command. [263:28] And I'm going to do Ctrl X. Yes. And [263:30] save it. If I do ls, I have the docker [263:33] file and I have a test.ext available on [263:37] the local directory. That's what I have [263:39] now. So let's go ahead and remove the [263:42] existing docker file. I could have [263:44] edited that but let's me let me just [263:46] remove it. ls. So I have only the [263:47] test.ext file. So now let's do one [263:50] thing. Let's do a nano docker file. [263:56] And I'm going to create from Ubuntu this [263:59] time. [264:02] And we can do run apt get updates just a [264:07] filler. And then we are going to do [264:10] copy. [264:12] I want to take the test.ext and move it [264:15] into a specific path within the [264:17] container. [264:19] So what we'll do is I'm going to copy [264:21] test.ext. So it will understand that [264:24] this is available on the local [264:25] directory. I could have also done it [264:27] this way or I could [264:32] just leave it this way. Both should [264:34] work. So this is the source. [264:36] So where do you want to take it? What's [264:38] the destination? I could have enter. So [264:40] it will be on the root of the container. [264:42] Or I can do in a directory called app. [264:46] So if it doesn't exist, create it for me [264:49] and copy the file into it. Or let's [264:52] choose another one. copy test app. So [264:57] this is going to be the folder. So we [264:59] are not going to confuse it with any [265:00] default ones that are going to be in the [265:02] container. And what I will do also I can [265:05] do cmd cmd and echo testing copy. All [265:11] right. So this is my docker file. I'm [265:13] going to do ctrl x yes and hit enter. [265:16] Let's do cat to the file to make sure [265:18] that it has what we need. So from Ubuntu [265:23] run apt update and then it's going to [265:26] copy this into a new directory that is [265:28] going to create and then cmd echo [265:31] testing copy. This could be unnecessary. [265:34] I could have just ignored it completely. [265:36] So let's build the image. [265:39] I'm going to call it image [265:41] copy. [265:43] And it's in the the build context is the [265:45] local directory. [265:49] And when I do this, that means that [265:51] test.ext is in the local directory as [265:54] well. So it's going to search for it [265:55] when I do the copy in the local [265:57] directory. [266:02] All right. So docker images [266:05] and we have the image copy here and [266:08] that's the size [266:10] and we can do a clear. And now let's do [266:13] docker run. I want to get into the [266:15] container to verify that that directory [266:17] has been created. and the copy has been [266:20] also executed and the file test.ext [266:23] exists on the container. Okay, so docker [266:26] run minus it and then image copy and I'm [266:31] going to run bash. [266:34] So now if we do ls you'll find that we [266:37] have the directory copy test app and if [266:40] we do ls copy test app you'll find that [266:46] there is a file called test.ext text and [266:48] if I do cat [266:50] copy test app test.ext [266:56] hi this is testing from or testing the [266:59] copy command. All right. So it's very [267:01] clear how handy you can use the copy [267:05] command because you want to add your [267:07] application, you want to add your code, [267:09] you want to add your dependencies, [267:11] requirements, files and so on and that [267:14] are these are going to be inside the [267:15] container because when the code runs [267:18] then it needs to access all these [267:20] information and these data and of course [267:21] the code needs to be existing as well. [267:24] All right. Hopefully that makes it clear [267:26] and it's easy to assimilate. [267:34] Still with Docker files and we are still [267:36] with the Docker file instructions. We [267:38] are going to look at work directory or [267:40] work dire and we're going to look at M [267:42] and the label instructions. So let's [267:45] dive straight in. That takes us to the [267:48] third instruction which is work [267:50] directory. What if I need to move within [267:52] the file system or do like a cd and then [267:55] a path within the image path or the the [267:58] container file system path while I'm [268:00] writing the docker file. So work [268:03] directory is used to define the working [268:06] directory of the docker container at any [268:08] given time [268:11] and the syntax is work dire and the path [268:14] that you would like to move within the [268:17] image p file system or eventually the [268:19] container file system. So the work dire [268:22] will create the directory specified by [268:24] path and runs the following container [268:27] commands. So when you do the work dire [268:29] this is equivalent to as if you are in [268:31] the container and you have done cd and [268:34] then the name or the path and if the [268:36] directory is not available this becomes [268:38] equivalent to as if you did m a mk or [268:42] make directory and then the name of the [268:45] directory and moving into that directory [268:47] as well. So as if you did make directory [268:49] and you moved into it. So make directory [268:51] and cd or if the directory is existing [268:54] because of a previous work directory [268:56] then maybe it's only a cd. So any [268:59] commands will come afterwards until you [269:01] hit another work directory they are [269:03] going to be implemented into that path [269:05] within the image and the container. So [269:07] if you copy files they will be copied in [269:10] that new work directory or the one that [269:13] you have created and moved into. So [269:15] let's look at an example when you do [269:17] work dire. So this is a snippet again. I [269:20] mean this there could be commands in the [269:22] docker file before and after work d / [269:25] app that means if the slash app [269:27] directory exists move into it. So [269:30] anything that I'm going to tell you [269:31] underneath this until you hit another [269:34] work directory instruction will be under [269:36] the slash app and the slash is abs this [269:39] is absolute. So from the root from where [269:41] it starts under app directory and if it [269:44] doesn't exist create it [269:50] the path in the syntax that refers to [269:52] the image and eventually to the [269:54] container file system. It does not mean [269:57] the host that you are working on. It's [270:00] not like the copy source the source path [270:03] was on the host and then the destination [270:05] was in the file system of the image. [270:07] This is 100% for the image file system [270:10] which will be the container file system. [270:13] So the path will be in the resulting [270:15] image during the build time and in the [270:17] container during runtime. So this is [270:19] very important such that you don't get [270:22] confused. [270:24] So let's look at a real example that [270:26] actually uses copy and work directory so [270:28] we can understand it better than before. [270:30] So the exact same project structure on [270:32] the docker host we have the working [270:34] directory. It could be /home/ Ubuntu. [270:38] And I have a Docker file under the same [270:41] directory. And then I have a folder [270:43] called app main.py [270:45] under this is a file under the app [270:48] subdirectory or directory. And then I [270:50] have another nested subdirectory under [270:52] the app directory that has a file called [270:54] helper.py. [270:56] Here is what we are going to do. So we [270:58] are going to load it from Python 3. I [271:01] believe this is a flask version if I'm [271:03] not mistaken the slim one. [271:06] Then we are going to create a working [271:09] directory where so working directory is [271:12] talking about exactly the image and [271:15] eventually the container from that image [271:17] not the local host. So if the slash [271:21] user/source SL app so basically from the [271:24] root this is an absolute path create [271:27] them if they don't exist. I want [271:29] directory from the root called usr user [271:32] and a subdirectory under that directory [271:35] called source and then a subdirectory [271:38] under that called app. So if I want to [271:40] draw it in the container, it's going to [271:42] be the root. And then under the root, we [271:45] are going to have user and then under [271:48] user, I'm going to have a folder called [271:51] src. And then under src, I'm going to [271:54] have a folder called app. And then I can [271:57] have files under that app or unders. So [272:00] I have this level, this level, this [272:02] level all nested together. And this is [272:04] the root of the container. That's [272:06] exactly what I did here. And what we [272:09] need to do now is we need to to copy the [272:12] content of the utils directory. Copy is [272:16] source and destination. Source is the [272:20] docker host. Destination is exactly is [272:23] the container image and eventually the [272:25] container. So I want to move this but I [272:28] want to move it under user source app [272:30] code. Okay. So under user source app I [272:34] also have another directory from here [272:36] called code and under code I have one [272:41] directory called utils. So this is the [272:44] structure that I have in mind and the [272:46] commands are going to facilitate this. [272:49] So the work directory user source app is [272:51] going to create this and this and this [272:56] and also since I did this now inside the [273:00] file system of the container it is as if [273:03] I have moved so I created all of this [273:06] and I have moved here so any relative [273:09] path that I'm going to provide should be [273:12] starting from the app any absolute path [273:15] can start from the beginning but I can [273:17] start from the app directory because [273:20] this has moved me inside the image or [273:23] the image to be to the app level. So now [273:26] I'm going to do copy app/utils and this [273:29] is going to be copied at user source app [273:32] code utils and if this doesn't exist it [273:34] will be created. So now the content is [273:37] going to be moved and it's going to be [273:38] under utils. So what it will will be [273:40] available here that will be the helper [273:44] py that's is what will be copied here. [273:47] Now all right so this is done now but we [273:50] are still here from a work directory and [273:54] from a file system perspective however [273:57] we have provided the absolute path so it [273:59] cannot confuse it another way I could [274:01] have done it is just slashcode [274:04] /utils or codeutills and it would have [274:08] understood that I'm talking about this [274:10] and about this if I wanted to go with [274:13] the relative path not the absolute path [274:17] now I want to copy just the main py file [274:20] and I'm going to move it into user [274:22] source app code. How can I do this? Copy [274:26] from this that's a relative path [274:28] according to the current directory from [274:31] a subdirectory under wherever I am in [274:33] the file system on the docker host from [274:35] the app uh directory please copy main.p [274:38] py where are you going to move it? I [274:40] could have said since I am right here in [274:43] the image file system I could have said [274:47] code slash and that's it. But here we [274:50] provided the full absolute path. So from [274:54] app/main. py please move it into user [274:58] source app code. So underneath this [275:02] directory there will be the main. py and [275:06] this is in the resulting image and in [275:08] the resulting container from that image. [275:11] So now we have moved our code as we like [275:14] it to be. So the application itself is [275:17] going to be under code and any utilities [275:19] any is going to be under utils which is [275:22] a subdirectory from code. Now I would [275:24] like to set the container directory from [275:27] here I would like to shift it to here. [275:30] So we can do this using another work [275:32] directory that will move me one step [275:35] lower in the hierarchy as if I did cd [275:38] space code. So get me into the code [275:42] directory or subdirectory in this tree. [275:46] So how would you do this? I would do [275:47] work directory/ user/source/ [275:50] app/code. So this was going to be the [275:53] container initial working directory when [275:56] we start the container. So if I log into [275:58] the container. So we create the image [276:01] and then we create a container from the [276:02] image and if I do docker exit and I get [276:04] into the container and do the command [276:06] pwd I should see that I am at the / [276:10] user/source/ app/code [276:13] that will be the meaning of what we are [276:15] doing here then what do you want to do [276:17] then I want to run a command what's the [276:20] command that you would like to run this [276:21] is a python code right so it makes sense [276:23] that I'm going to either use entry point [276:25] or use command and the command will be [276:28] python 3 and The application I would [276:30] like to run is main. py. If you didn't [276:33] do the work directory, then you should [276:36] have added that it is under code /ain. [276:40] py in order for the path to be right. [276:44] Otherwise, you'll get an error. We [276:46] preferred that we move into that [276:48] directory beforehand so we can just do [276:51] main. py and it works. So hopefully this [276:54] is clear right now on how copy and work [276:57] directory they function together. [277:00] And here's another docker instruction [277:02] called environment. So that allows for [277:04] setting environment variables for the [277:06] docker container. The syntax is env and [277:09] then the key and the value for that key. [277:12] That's how we write it. So here's an [277:14] example. We have env [277:18] name equals dolphin at. So this is the [277:21] key and that's the value assigned to [277:23] that key. So now as if I'm defining a [277:26] variable and a value to the variable. So [277:28] now whenever I use it within the docker [277:32] file, I don't have to rewrite dolphin ad [277:35] again. So I can just do command echo and [277:38] then dollar sign the key and that will [277:41] immediately as if I am referencing the [277:43] dolphin ad parameter. So imagine this is [277:46] an IP address that you would like to use [277:48] it or a URL that you would like to use [277:50] it or a parameter or port data that you [277:53] are using multiple times inside the [277:55] docker file then you can reference it [277:57] once in the environment and then just [277:59] use its name as a variable. So this one [278:01] when we create an image and from which [278:03] we create a container the container will [278:06] echo dolphin ed which is the [278:09] corresponding value. So what if we would [278:12] like to override the defaults or the [278:15] values that we have assigned to the keys [278:16] in the in commands in the docker file. [278:20] Can we do this? And the answer is [278:21] absolutely you can do this. And here's [278:23] an example. What we need to do is we [278:26] will we need to build a container that [278:28] will do some let's say TCP IP checking [278:31] or HTTP checking. So for that one we're [278:35] going to run two env commands. One is [278:38] going to be for the action equals pink. [278:39] Here is the key. Here is the value. And [278:41] the other one target equals 8.8.8.8. [278:45] So two keys and two values assigned one [278:48] to each. And then we are going to run [278:51] the command shell. [278:55] The image is alpine [278:57] and treat the string here as a command. [279:03] So that will be execute and assign [279:06] process ID one dollar sign action. So [279:08] basically the value of action and dollar [279:11] sign target the value of target that's [279:13] the default. If I don't do anything else [279:15] this is what will be executed. [279:17] So let's build the image [279:20] and then we are going to execute it now [279:23] to run a container because we need to [279:25] ping a specific target. So for that one [279:29] we can do docker run my image and that's [279:32] it. By the way, the Alpine is a very [279:35] light image and usually it doesn't have [279:38] the ping and the curl installed. So [279:40] that's why run app [279:44] this is in Alpine. This is similar to [279:47] run app get install in Ubuntu. [279:52] So Abuttails is going to install pink [279:54] and curl is going to be installed by [279:56] this one. Now if I would like to use [279:58] curl to a specific IP address, what do I [280:01] do? Then we can override the default [280:04] value ping for the action by using the [280:08] hyphen e with the docker run command. [280:10] It's an option for docker run. So action [280:12] equals curl. That means please take curl [280:15] as the value for action. Do not take the [280:17] default one. And please take minus e [280:21] also minus environment target. So the [280:24] environment target take the value for [280:26] that as 10.10.1.1 [280:29] instead of 8.8.8.8 8 my image and the [280:34] output is going to be without the E [280:36] option at runtime we know that is that [280:39] is going to be ping 8.8.8 but with this [280:42] command it will be curl 1010.1.1 [280:45] the shell will invoke a shell inside the [280:47] container and the minus C tells the [280:49] shell to run the following string as a [280:51] command. So this string is going to be [280:53] run as a command. All right. [280:58] So the label instruction has been used [281:02] now after the maintainer or the author [281:05] has been deprecated. So the label is to [281:08] put a label metadata basically to your [281:11] image while you are creating it. So you [281:14] can add metadata to an image. So the [281:16] label is going to be in the docker file [281:18] another instruction. The metadata that [281:20] you can add includes a lot of things. It [281:22] could be including who's the author, [281:24] who's the maintainer, what's the [281:25] version, what's the email of or the [281:27] telephone number of the team that [281:29] supports it, environment, production or [281:32] else other custom data that you like and [281:34] it should be written as key value [281:38] and here's an example label and the key [281:42] is owner and what is between the codes [281:46] is all the value. So, Dolphinet Academy [281:49] team and here's the email team at [281:51] supportthedalfphanet.com and we could [281:52] have a phone number or a WhatsApp number [281:54] and so on. Let's now do a hands-on lab [281:57] to demonstrate the instructions in the [281:59] Docker file work directory environment [282:02] or M and label and how they work. Let's [282:06] get to the console. All right, so ls I [282:10] have here the docker file and test.ext. [282:12] So, let me go ahead and remove the [282:15] docker file. [282:19] All right. And I'm going to remove also [282:21] the test.ext. [282:28] So as usual, I have the two terminals [282:31] and I have cleaned completely the docker [282:34] host. So if you look at docker images, [282:36] you'll find only a few left. And if we [282:38] do docker ps minus a, you'll find that [282:41] there are no containers active up or [282:44] exited. [282:46] All right. So, let me clear. And if I do [282:48] ls as well, I don't have any files [282:50] available on the docker host. So, what [282:53] do we need to do? I need to explain [282:56] three different commands today. And [283:00] again, everything is available in your [283:01] script. I'm trying to follow the same [283:04] steps because it will make it easier for [283:06] you as well to follow along if you watch [283:09] the video or if you want to reference [283:10] the script. And all the scripts are [283:12] going to be available to you. So, don't [283:13] worry about that. All right. So what do [283:15] we need to do? We need to create a [283:16] docker file. And now we are going to [283:19] demonstrate the work directory. [283:24] And here I'm going to start from Ubuntu. [283:29] So we are going to do work directory and [283:31] / app. So basically as if I'm [283:35] instructing docker when the container is [283:38] to going to be run that please create an [283:41] app directory that is below the root [283:44] directory. Then we're going to run echo [283:47] command. And what we will echo is this [283:50] is the / app directory. [283:57] And this will be redirected into [284:01] uh file. [284:04] Let's call it app.ext. So the same name [284:07] as the folder. All right. So that's one [284:10] run command. Then we're going to do [284:11] another work directory. So I'm going to [284:13] create a path within. I'm going to say / [284:16] app slashcode for example. And then [284:20] we're going to run an echo command [284:22] again. Run echo. [284:25] And similarly we're going to state that [284:27] this is [284:29] the / app [284:32] slash app slashcode [284:36] code directory [284:39] directory. [284:40] And also we're going to redirect that [284:43] into a file called code.ext [284:47] or we can do even appcode.ext. [284:55] All right. [284:56] And then we can do an echo although it's [285:00] not that important [285:03] in the command or I can do just ls at [285:05] the end. [285:07] ls. So I don't have to provide any [285:10] parameters or any arguments. And I'm [285:12] going to do a control x yes to save and [285:15] enter to get out. And let's do a docker [285:19] uh a cat to the docker file. [285:22] And here it is from Ubuntu work [285:24] directory. So cd basically into an app [285:27] directory and then create this file. And [285:29] then it's going to do a cd again into [285:31] code and then it will create this file [285:34] and it will do an ls when I run the [285:37] container. [285:39] Okay, that's fine. Docker build minus t [285:45] image work dire [285:51] and it is in the current directory. The [285:53] building context is in the current [285:54] directory. [285:58] It sounds good. Docker images. [286:01] We have it. What a short name. I'm going [286:04] to copy it because I need it. Clear [286:07] docker run- it and the image. And the [286:13] command we are going to execute is bash. [286:16] So I'm now inside the container. Have [286:20] you noticed what happened now? The last [286:22] thing we did in the docker file was I [286:25] mean we moved into the app directory [286:27] with the first work dire/app and then we [286:30] did another work dire /app /code. So it [286:34] had created an app folder under the root [286:38] and then a code directory under the app [286:41] directory and now I am into that path [286:45] inside the container. [286:48] All right. So let's see let's me do ls [286:53] and you have the app code text. So let's [286:55] cut this file app hyphen code [286:59] dot text [287:02] dot text [287:04] text. Yeah. And you find that this is [287:07] the app code directory. So not only the [287:10] directory and subdirectory have been [287:11] created but also the app code file and [287:14] also the redirection of the echo output [287:17] in the run command into this file. So [287:20] let's do a cd move one step up in the [287:23] hierarchy and you'll find that we moved [287:25] now into the app directory. If I do ls [287:28] then we have a directory called code [287:30] which we were in and we went one uh step [287:34] up and then there is the app text. So if [287:37] I cat the app.ext.ext [287:42] then this is the app directory. All [287:45] right. So that explains to you how you [287:47] can control your working directory using [287:52] the docker file. I do exit now. [287:56] Now let's the docker file and let me [287:59] change the default starting path. [288:04] How would you do this? I'm going here to [288:06] add a command that says work directory [288:10] and I'm going to start [288:13] at the app but I'm going to call it [288:17] database for example. [288:20] So now we moved into app and then we [288:23] moved into app code and now I'm going to [288:25] move into app database. That is one [288:28] thing I can do as well. All right. So [288:31] let's do Ctrl X Y enter. And I'm going [288:34] to build the image again. And I'm going [288:37] to build the image again. [288:40] We'll call it amage work dire 2 [288:48] the build context. So dot [288:52] docker images [288:55] and we have it work dire 2. I'm going to [288:58] copy the name clear and let's start a [289:01] new container [289:03] docker run minus it and the image name [289:08] and I'm going to do a pwd [289:11] so print the working directory [289:15] you'll find that we are into the app [289:18] database so we are not we didn't open [289:20] the interactive I mean if I didn't have [289:22] this it would have worked as well but [289:24] here it tells you that the default of [289:25] the container is app database how can [289:27] Let me confirm. [289:29] I'm going to do bash. [289:31] And here we go. So you started at the [289:34] app database. So this is very clear how [289:36] the work directory work as if you are [289:38] moving moving and you can build your [289:40] file system the way you like it and the [289:42] way you would expect it to run when the [289:44] container is created from that image. [289:47] Hopefully this is clear. All right. [289:49] Let's now go ahead and do the M and [289:52] label. [289:54] So here we go. I have the two terminals [289:56] available and ls I don't have any files [289:59] available. What are we going to do? I [290:01] want to do them both in one docker file. [290:04] So let's nano a new docker file [290:08] and it's going to be from Ubuntu. [290:12] And I'm going to run app get update [290:17] and I'm going to also run app get [290:20] install minus y. And what I need to [290:24] install is the IP IP utils ping because [290:29] we need to use ping in this case. And [290:32] I'm going to do m and I'm going to call [290:34] action equals ping [290:38] and target is going to be 8.8.8.8. [290:43] So what what I'm trying to do is when [290:46] the container runs I would like to ping [290:48] the IP address 8.8.8.8 8 basically [290:51] sending messages to that IP address and [290:53] waiting for responses or an echo [290:56] response. 8.8.8.8 [290:59] is the Google DNS server and it's [291:02] available on the internet and anybody [291:03] with connectivity to the internet can [291:05] ping it. [291:07] All of that is good. Then I'm going to [291:08] do label. Who is the maintainer? Who [291:10] created this? Who is the author? And I [291:12] would say dolphin ad docker [291:16] team. [291:19] And we need to execute the command. So [291:21] we're going to use bit of a complicated [291:24] format. So it's going to be shell [291:26] expansive. [291:27] And I'm going to have the minus C for [291:31] what will be uh implemented. And for [291:34] this one we are going to use [291:38] the dollar sign action [291:41] and dollar sign target [291:45] and then we close this. So basically [291:47] what I'm trying to do is when this runs [291:50] it's going to install the ping utility [291:53] inside the container and these two are [291:56] like variables a variable called action [291:58] equals ping. So that's the key and the [292:01] value and there is another one target [292:03] key and the value [292:06] and the label is only going to talk [292:08] about metadata of the image and then we [292:10] have the cmd. The cmd is going to run [292:12] this as a shell. So it's going to have [292:16] the action [292:18] which is ping and then it's going to run [292:21] the target which is 8.8.8.8. So [292:24] basically these are going to be replaced [292:26] and this is going to be the command to [292:27] be executed in the shell. All right. So [292:31] let's do ctrl x yes enter. And we're [292:34] going to build the image [292:38] minus t. I'm going to call it image [292:42] one, two, three for simplicity. And the [292:44] build context is the local. [292:47] All right. It has a minor comment about [292:49] the label. We're going to look at that [292:51] later on. Docker run. And then I'm going [292:54] to run this from the image. Image one, [292:58] two, three. Let's see what happens. [293:01] Let me nano the file again. [293:04] All right. I think I know where the [293:06] problem is. [293:08] This does not exist. [293:14] So I'm going to do Ctrl X. Yes. And try [293:17] again. [293:19] Docker build [293:22] minus T. [293:24] Correct. I'm going to call it. And the [293:27] build context is local. [293:30] Docker run. Correct. [293:35] And as you can see the container has [293:37] started. And now it is pinging 8.8.8.8. [293:41] So it has worked. It was only the square [293:43] bracket, the extra one that I have [293:44] added. But you have it correct in your [293:47] syntax. So don't worry about that. And [293:50] it shows that the container has started [293:52] and the cmd is pinging now the DNS in [293:56] Google. All right. Of course, I will not [293:58] be able to stop it from here. So what I [294:00] will do is I'm going to do on the other [294:01] one on the other terminal. That's why [294:04] it's handy docker ps. And I have the [294:06] container running. So I can stop the [294:08] container or I can just remove it [294:10] because I don't need it anymore. So 182 [294:12] the first three letter from the [294:14] container ID [294:17] and I have to do minus f because it is [294:19] running [294:22] and now it should stop. So if I go back [294:25] you'll find that I'm back. The prompt is [294:27] here again. All right. So that explains [294:30] the label and explains the m. So let's [294:33] nano the docker file [294:36] and look at the problem we have seen the [294:39] label issue that it didn't like and what [294:43] it expects is it doesn't expect to see [294:46] the input this way it has to be in a key [294:50] value format. [294:54] So let's do maintainer and it equals and [294:58] I'm going to say dolphin ed academy [295:03] team. And if we want also we can add an [295:06] email. So let's say for example dolphin [295:09] adolphin.com. [295:13] So this way it's not going to complain [295:15] about it. And let's verify. Ctrl X. Yes. [295:20] And let's do a docker build. If it [295:23] doesn't complain, then we should be [295:24] fine. [295:26] Minus t image 1 2 3 4 and local. [295:33] Yeah, it didn't complain about it, which [295:35] is good. Let's do docker inspect [295:39] and image 1 2 3 4. [295:44] And if we look at labels, [295:49] yeah, see labels maintainer, dolphin [295:53] head academy team and the email. So now [295:56] all is cool, everything is good and this [295:59] is how it should be written. [296:07] Now let's talk about docker images and [296:09] docker registry. I think we have covered [296:11] a lot about Docker images already. But a [296:14] quick recap and then we'll head into [296:15] Docker registry. How can we create our [296:18] images but then not stop at that point [296:20] but we can push it into a repo of our [296:23] own. It could be a public one, it could [296:25] be a private one or we have already [296:28] pushed images and now it's time to pull [296:30] images from our own repo public or [296:33] private. So let's go ahead and start [296:35] with this. Let's start first with Docker [296:37] images. A quick recap. We have already [296:39] covered a lot of information about that. [296:42] Please remember that we called the build [296:44] time which is where we have a docker [296:47] file and then we build an image from the [296:49] docker file using the docker build [296:51] command. [296:53] So we have the docker file from which we [296:56] can use the docker build command and [296:57] then we can tag the image with the name [296:59] we need and then we define where the [297:01] build context is and what it will do [297:04] what docker will do is it's going to go [297:06] ahead and create different layers one [297:09] corresponding [297:10] to each of the commands in the docker [297:13] file and of course from this will not [297:16] bring one layer it could bring one two [297:18] three seven 19 layers depending on how [297:21] How many layers does the image you are [297:25] pulling from contain? So how many layers [297:29] basically that image includes? [297:31] Image layers when you build it are read [297:33] only. So you cannot edit them. If you [297:35] need to make a change, you will have to [297:37] update your docker file and then you'll [297:39] have to create a new image with a docker [297:42] build command. [297:46] So docker image layers, what's the best [297:49] practice? what to do with these layers [297:52] in order to optimize the image. So you [297:54] need to group the copy and run wisely to [297:57] improve layer caching. So if you have [297:59] multiple copy commands, can you combine [298:02] them and at the same time you are sure [298:04] that these are not going to change [298:05] frequently in one or two layers or less [298:08] number of layers in a way that caching [298:11] is going to be effective and at the same [298:14] time it will not change every time like [298:16] these layers will not change every time [298:18] you make a change. You need to put less [298:20] frequently changed lines early like [298:23] installing dependencies for example. So [298:25] up in the docker file after the from if [298:28] you have less frequently changing [298:30] dependencies for example downloads then [298:32] put this at the top. [298:34] Avoid unnecessary run commands to reduce [298:37] layer count and image size. Like in the [298:39] examples we have seen when we do run app [298:42] get update and then a separate line run [298:44] app get install minus y vim and then a [298:47] third line apt [298:50] run apt get install minus y get and then [298:54] run. So you can combine these into one. [298:57] So they will be one layer and you will [299:00] enhance the image size and so on. So [299:02] back to the best practices again. Let's [299:05] see what is the goal and what is better [299:08] and why. For example, if you would like [299:10] to have fast builds, the image does not [299:13] take much time. Then we need more layer [299:16] because that will have the different [299:18] details cached. And now if we would like [299:20] to build again, a lot of the cached [299:23] stuff will not be rebuilt again. It will [299:25] be reused and then we'll only build the [299:27] new stuff or the changed stuff. [299:30] So this will allow Docker to skip [299:32] unchanged layers. If you need smaller [299:35] images, then we need fewer layers and [299:37] clean builds. Why? Because this is going [299:40] to have fewer intermediate file sizes or [299:43] layers. We need to enhance the [299:46] maintainability readable layers. So we [299:49] need easier debugging and edits. So this [299:52] will be easier for readability and that [299:54] means easier debugging and edits. [299:58] For layer reusability, [300:01] what's better is to split steps [300:04] logically. So it's not always to reduce [300:06] the layers. Maybe you will split the [300:08] steps because you would like to reuse [300:10] and when you reuse, you would like [300:12] caching to be effective as well. So in [300:14] that case, maybe you will have more [300:16] layers and that will have base images [300:18] that can be reused and cached. All [300:20] right? So it's not like one way, but now [300:23] you have the best practice. Keep it in [300:25] mind. Of course, fast builds are [300:27] important, smaller images are important, [300:30] maintainability is important and also [300:32] reusability is very important. [300:37] So from the build time we take it to [300:38] runtime and this is when we start to [300:40] create our containers [300:43] or the execution phase of the [300:45] containers. [300:47] So the image we have built is going to [300:49] be used to create the container and [300:51] execute the command or the entry point [300:53] command that is in the image or the if [300:57] we can override it then the one provided [300:59] at runtime basically and that will [301:02] create the container once the container [301:04] is created if we have an exit [301:07] interactive shell into the container. So [301:09] these are locked because they are only [301:11] readable or read only but then we might [301:15] do an update. I might install another [301:17] tool ping touch or one that I will need. [301:20] In that case I can create more layer [301:22] using these commands and these will be [301:24] writable container layers because they [301:27] are not part of the image. I have [301:28] created them when I created the [301:31] container manually. [301:36] Please remember the image tag the image [301:38] version basically that we can tag images [301:41] as we upload them or as we pull them as [301:44] well. we can tag what we need to pull or [301:46] when we are uploading them to docker hub [301:49] we can also or to the docker registry we [301:52] can also decide this is version one this [301:54] is version two this is version three and [301:56] we can have also messages that goes with [301:59] that or metadata that would would state [302:02] why did you do the change [302:06] so if we do docker run postgress 10 10 [302:12] anything after the colon is the image [302:14] version if we don't add anything that [302:16] becomes the latest. But if we do this [302:18] then what will happen is if I don't have [302:20] it locally that means docker is going to [302:23] go ahead and get version 10.10 [302:27] and if we do docker run for that one you [302:30] will see that it could not find it [302:32] locally and now it is pulling it and [302:34] it's pulling its layers as well. [302:38] Whereas if we do docker run postgress [302:41] without the colon latest or with the [302:43] colon latest it's the same thing it will [302:45] go ahead and pull the latest version of [302:49] postgress. If we have done that [302:51] beforehand what you will see here is [302:54] some of the layers are not going to be [302:56] pulled again because they do exist. So [302:59] if they did exist on your local system, [303:01] they will be reused because of the [303:03] caching and now it will only pull the [303:07] layers that didn't exist or they are [303:08] different than 1010 [303:13] and postgress 1010 will do the same [303:16] assuming that 11:15 was the latest for [303:18] example. Let's now discuss docker [303:21] registries. This is the place where we [303:24] store the images. So this is where we [303:26] push the images we created from our [303:29] virtual machines or our laptops into the [303:32] registry such that it's going to be [303:34] available to everyone else that is [303:37] allowed to access it and use it. If it [303:39] was public registry then everyone with [303:43] the right command can pull that from [303:45] your registry. If it was a private [303:48] registry then anyone who can login or [303:50] access or have credentials to get to the [303:52] registry would be able to pull the [303:55] images. [303:57] So pushing images as we mentioned if we [304:00] would like to visualize this is [304:01] basically about having an image created [304:04] somewhere and then you need to do a [304:06] docker push and the docker push command [304:09] is going to take that and then push it [304:11] to the repository in the registry that [304:14] you have specified by default and the [304:17] most common one that everyone uses and [304:19] it's available for everyone is docker [304:21] hub [304:23] and in docker hub we can have under your [304:26] account it can be a public repo or [304:28] multiple public repos or you can have [304:30] one private repo if it was a free [304:32] account or multiple private repos if it [304:35] was a paid account. There is a specific [304:37] naming convention for Docker images that [304:41] helps with organizing [304:43] versioning and discovery of images. [304:45] What's the naming convention? It's [304:47] exactly as we see here. So the registry [304:50] name or the DNS of the registry and then [304:53] we have the account or the organization [304:57] and then we have the repository and a [305:00] tag. So the repository can be the image [305:02] name as well. So let's get to know each [305:04] one of them in more details. The [305:06] registry is optional. Why optional? [305:08] Because if I'm dealing with Docker Hub, [305:10] I don't need to specify it. It defaults [305:12] to docker.io. That's the default. [305:15] Otherwise, if you have a registry that [305:17] you have established inside your [305:19] corporate or you're using something else [305:21] other than Docker Hub, then you'd like [305:23] to add the domain of the container [305:25] registry. Basically, how can we resolve [305:29] that to an IP address to find out where [305:31] is your registry then the second part [305:34] this is the name of the user or [305:36] organization and it is required for [305:38] nonofficial images only. official images [305:42] like EngineX, Ubuntu, Red Hat, CentOS, [305:45] Fedora, Alpine. These are all known [305:48] official images from Docker. Then they [305:51] don't need the organization and we don't [305:53] need the registry because they are on [305:54] Docker already. Then we have the third [305:57] part which is the repository and that is [305:59] either the name of the image or the [306:01] project. For example, production [306:04] e-commerce that's a name of a project or [306:06] it could be app 1, app 2, app 3. So [306:09] that's the name of the image and then we [306:11] can have a tag as well because we need [306:14] to maintain versions of that as changes [306:17] happen [306:18] and if you don't add a version or a tag [306:21] it will default to latest if that is not [306:23] included. [306:26] So let's say I have an image called ABC. [306:29] Is there a way I can create or rename or [306:33] create an alias of that with the correct [306:35] name that is that follows the naming [306:37] convention uh for Docker images? And the [306:39] answer is absolutely and that's the [306:41] docker tag command. So the syntax is [306:44] docker tag and then the source image and [306:48] the corresponding tag if this is what [306:50] you need to rename and then the target [306:52] image the new name and in the new name [306:54] you can control to make it according to [306:57] the naming convention of the docker [306:59] images and then a tag if required. [307:03] Here's an example docker tag python [307:08] 3.10. [307:10] I'm going to change the name to my [307:12] Python hyphen app and latest. This is [307:16] general usage. So using the tag command [307:19] to create an alias or to add a name to [307:22] an image does not mean this is only if [307:25] you want to push images to a docker [307:28] registry. You can or you may want to [307:31] change the name and use the new name. It [307:33] will be the same image. It will not be [307:35] copied. It will not create a new image. [307:37] But there will be another name for the [307:39] image that it can be accessed through. [307:44] Now if we would like to use the docker [307:46] tag with docker registries. So the [307:49] motivation now is we would like to push [307:52] or upload the image to a docker [307:54] registry. So we have now to follow the [307:57] naming convention. So in that case you [308:00] will use the source name and tag if any [308:03] and then we are going to follow the [308:05] naming convention. So it we have to [308:07] specify the registry unless if it is [308:09] docker hub then we don't need to then [308:12] what's the username or the account and [308:15] the repo tag that's for the image and [308:18] repo which account and which repo to use [308:21] in that account and what will be the tag [308:23] or the version of that. This is only [308:26] about tagging changing the name creating [308:29] an alias. This is not the actual push. [308:32] Let's look at examples. [308:35] Dogger tag my app. So this is the source [308:39] image. There is no colon latest or any [308:41] version. So it will be considered as [308:43] latest. And this is it's not docker hub. [308:47] So that's the registry that we are going [308:49] to use. So this is the domain of the [308:50] registry. And this is the account. And [308:54] here is the image name. And I would like [308:57] to tag it with this version. [309:00] So I maintained the image name as is. So [309:03] I have a repo on this registry called my [309:05] app [309:07] and this is the version that I would [309:09] like to tag it with. So this will tag [309:11] the image my app with the name [309:13] registry.mmyorp.com [309:15] devops my app 1000. So this becomes the [309:19] new name or the alias of this image and [309:22] this is what we are going to use when we [309:24] try to push because it will tell the [309:28] demon where we are going to upload it [309:31] under which account and what's the name [309:33] of the repo. [309:35] To push commands into a registry you [309:37] have to login or authenticate otherwise [309:40] anyone will be able to push images into [309:43] your registry. [309:46] to push images into your registry [309:48] whether it is public or private doesn't [309:50] matter you have to authenticate with the [309:52] registry so you have to have credentials [309:54] to be able to upload or push into the [309:56] registry and the way you do this is very [309:59] simple from the CLI on the docker host [310:02] docker login and then the name of the [310:05] registry then you will be prompted for [310:08] the username and the password and then [310:10] you will be authenticated once that is [310:12] successful you will be able to push to [310:14] the registry [310:16] If we are working with docker hub [310:18] registry the docker tag command we don't [310:22] need to put or to add the registry [310:25] domain. [310:27] So it will be only docker tag local [310:29] image name and the local tag and then [310:32] the username on docker hub and the repo [310:35] and tag on dockerhub. So why didn't I [310:38] add the registry? Because it defaults to [310:41] docker.io as we mentioned before. So it [310:43] will be simpler name that you are using [310:47] or the alias name is going to be simpler [310:49] by one step. No registry details. [310:53] Here's an example. Docker tag my image. [310:56] This is the account I have on docker hub [310:58] and that will be the repo. Please note [311:00] that they don't have to be the same [311:02] name. So they may or may not be the same [311:05] name. And then the version on docker hub [311:08] in the repo. So this is going to be the [311:10] latest. So my image is tagged in [311:12] preparation of pushing to docker hub [311:14] registry. How did we know it's Docker [311:16] Hub? I did not specify anything here. So [311:18] it will default to docker.io. Under this [311:21] account under the repo my app with the [311:23] tag latest. [311:26] The local image name and the repo name [311:28] can be the same. They do not have to as [311:30] we mentioned. So here is another one [311:34] that docker tag my image and then my [311:36] username my app version one. So this is [311:39] if you wanted the latest and this is if [311:42] you wanted to add version one to be [311:45] pushed basically or it will be prepared [311:47] to be pushed as version one. [311:51] Okay. So now we did the tag whether it [311:53] was with a registry that has nothing to [311:55] do with docker hub or it is with docker [311:58] hub. Now how can we do the actual push [312:01] the actual upload to that registry is [312:03] using the docker push command. So the [312:05] docker push syntax is docker push [312:08] registry host. This part is not needed [312:10] in case if you are working with docker [312:14] hub and then the username and then the [312:16] image or repo. This has to come after [312:20] you have done the first step which is [312:22] docker tag. So you do docker tag first. [312:25] You rename the image properly and then [312:28] you push it. So you are not here trying [312:30] to rename anything. you have already [312:32] tagged it and it's available and now [312:34] it's time to push it to uh docker hub or [312:38] else depending on whether you included [312:40] the the registry host or not. [312:44] So here's an example for dockerhub [312:45] docker push my app and then my username [312:49] my app latest. [312:51] What if it is a generic registry not [312:54] docker hub something else then you will [312:56] tag the image properly in the previous [312:59] step and now push it with this name or [313:03] the alias which you have done beforehand [313:05] and you included the registry with it as [313:07] well. So this is the account and this is [313:10] the repo. Now putting all this stuff [313:13] together what is a docker image life [313:15] cycle? So we're just recapping [313:17] everything we learned about docker [313:20] images. So starting from a docker file, [313:22] we can use docker build in order to [313:25] establish an image. But of course [313:27] beforehand we must have a local host or [313:30] a docker host available. [313:33] So docker build will help us create the [313:36] image [313:37] or we can pull an existing image if you [313:40] would like to from docker hub or maybe [313:44] because we're using from Ubuntu so this [313:46] part is going to be pulled if I don't [313:48] have it locally. Now we end up with the [313:51] docker image. [313:54] From the docker image we can do docker [313:56] run or docker create. Then we end up [313:59] with a container. If you use docker run [314:01] it will be active running. [314:04] If you use docker create it will be [314:06] stopped. [314:08] Then we can stop start or restart the [314:12] container. [314:15] And we can do docker commit. If we did [314:17] some changes and we'd like to create a [314:18] new image, we can do docker commit. Of [314:20] course, it's always advisable that you [314:22] update the docker file and then you use [314:25] the docker build to create a new version [314:27] of the image. [314:32] And of course, we can tag it using the [314:33] docker tag command and then we can push [314:36] it to docker hub just to maintain it [314:38] there so it's not dependent on a virtual [314:40] machine or a docker host that may fail [314:42] and then the image will be lost. We are [314:44] going to demonstrate how we can push [314:48] images that we have to docker registry [314:51] and also how to pull images from the [314:53] docker registry if needed. So what we [314:56] are going to do is we have dockerhub and [314:59] we have showed how we can create an [315:00] account on docker hub and we are going [315:02] to establish an image or create an image [315:05] on the docker host. So let's call that [315:08] dh docker host. [315:10] Once we have the image ready, then we [315:12] can push it to the Docker Hub repo of [315:15] our choice. So let's go ahead and do [315:18] this in the Docker Hub host console. So [315:22] here I am logged into the terminal for [315:26] the Docker host and from a previous lab [315:30] we had an application, a Python [315:32] application that had a Docker file and [315:34] the rest of the data. If you would like [315:37] to look at the Docker file, we can [315:40] basically nano and then the Docker file. [315:43] I think I did a mistake. [315:46] There was an R missing docker file. So [315:49] here is the Docker file. So we're not [315:51] going to change anything. I'm going to [315:53] create an image from this. So I'm [315:55] calling docker build [315:58] minus T and I'm going to call it repo [316:01] image. Of course, I did not specify the [316:04] build context. So, it's going to be [316:06] local. [316:07] We do docker images. [316:10] I will find that I have a repo image [316:12] right here and it's latest because I [316:14] didn't tag it with anything and it's 8 [316:17] mgabytes because it's from Alpine. Now, [316:20] what I need to do is I need to move it [316:22] into Docker Hub. I need to push it to [316:24] DockerHub. So, in order to push it to a [316:27] Docker Hub, I need to tag it in the [316:31] format of DockerHub, right? So let's [316:34] check the DockerHub account that we [316:36] have. So we'll go to hub.docker.com. [316:41] I'm not signed in [316:43] at all as you can see. So there are [316:46] multiple ways to do this, but let me [316:48] sign in the normal way first. [316:56] The password. [317:01] So now I am into docker hub and as you [317:04] can see we don't have a repos available. [317:08] I can create one from here or when you [317:10] are pushing you can create that. So [317:13] docker hub will create that for you if [317:15] you are logged into this. [317:18] So what I can do is I can state that [317:21] this is going to to be called [317:23] app one for example. You can add a short [317:27] description. This is the Python [317:30] Python app that is created [317:35] using Python [317:38] Flask [317:40] framework [317:43] and I'm going to hit on create. [317:47] So now we have the repo but as you can [317:49] see we don't have any images. It's [317:51] blank. And the repo name here is the [317:55] account lab user 0701 and app one. This [317:59] is enough if I would like to push an [318:01] image into it because it's in docker. [318:04] All right. So we have seen that we have [318:06] the repo available and what we need to [318:09] do now is again a last look at the [318:12] images and as you can see we have the [318:14] repo image available. So what I need to [318:17] do now is I need to tag it because I [318:19] need to push it into the Docker Hub [318:22] repository that we have created. One [318:24] thing you need to notice here that if I [318:26] go back to repositories [318:29] that you can tell whether this is a [318:31] public or a private repo from here from [318:34] the actual folder or the actual section [318:38] of the repositories. [318:40] So let me go back here and what we'll do [318:42] now is I'm going to tag this repo the [318:46] repo image [318:48] with [318:50] lab user 701 / app 1 which is the name [318:55] that we have created right here [319:00] and I can do this as version one. So [319:03] let's see what happens. Now let's go [319:07] back to images. You'll find that I have [319:10] one here and the tag is version one. But [319:13] you will notice that the ID is exactly [319:15] the same like the previous one. And this [319:17] proves that this is nothing more than a [319:20] reference, a link or an alias to the [319:22] original one. Even the size is exactly [319:24] the same. All right. So now let me nano [319:28] the docker file [319:32] and I'm going to make a slight change [319:35] and let's say for this one I'm going to [319:37] say that the command is echo [319:41] and we are going to echo this is [319:49] app one version two [319:53] x yes and Enter. So now we have a [319:57] different Docker file. So what I will do [319:58] is I'm going to build a second image [320:02] and this is also going to be called repo [320:06] image. In this case it's version two. [320:09] And this is what happens in production. [320:11] We are simulating what happens. A change [320:12] happens or a change is needed. We go [320:15] update the docker file and then we [320:17] create a new image. And then if this is [320:20] going to be production or a lot of [320:21] people need to access it and also to [320:24] secure that image, we push it into [320:27] DockerHub. That's what we always do. [320:30] Okay, the build context. [320:33] So now we have the second image and if I [320:36] do docker images, [320:39] I'll find that I have repo version two. [320:42] So what I need is I want to eventually [320:45] be able to push it as well. So I'm going [320:47] to tag it repo image version two and I'm [320:52] going to tag it with lab user one [320:54] version two as well. So it's the same [320:56] application but this is a different [320:58] version. [321:00] And if I do docker images again [321:03] so what do we see here? Let's analyze [321:06] this. So repo image that was the [321:08] original one from which we created [321:10] version one. They both share 100% the [321:14] same image ID. [321:16] Then we created a repo image version two [321:20] and that has a new ID because it there [321:23] was a change made and that's a new image [321:26] a new actual image and this is the [321:28] reference or the alias of the new actual [321:31] image. So now we have two different [321:33] original images and two different [321:35] aliases and now I can think about why [321:38] don't I go ahead and start to push them. [321:41] Okay, so let's clear. [321:43] All right, what do I need to do now? I [321:45] need to start pushing the images. So let [321:47] me do docker images again. And now I [321:50] will start to push [321:52] and I would like to push this first one [321:55] first [321:57] v1. [322:00] So it is preparing now but at the end it [322:04] did it wasn't so happy. Requested access [322:06] to the resource is denied. So that's the [322:08] error we got. Since this is access [322:11] denied right now then I need to login. [322:14] And if you think about it, anyone trying [322:17] to access or push images in your repo, [322:19] they should be logged in. They should [322:21] have permissions, right? Otherwise, each [322:23] one will be able to push into every [322:25] other one's repositories and it's going [322:28] to be a mess. So, we need to login in [322:31] order to be able to do that. So, I'm [322:33] going to do docker login. I can do minus [322:36] u and I can put here lab user 701. [322:41] Now it needs the password. [322:44] Login succeeded which means I should be [322:47] able to push without any problems now. [322:52] So now it's preparing things are being [322:54] transferred [322:57] and [322:59] all right. So it looks like we have an [323:01] image that was pushed successfully. And [323:04] if we go here and we click on this, [323:09] we should see version one here. And it's [323:12] less than a minute ago. If I click on [323:14] the version on the tag, this is the [323:16] Docker file. This is the original one [323:18] before we made that change. And that's [323:20] why the command is the original one as [323:22] well. If I go back and if I want to pull [323:26] this one, then I should be able to pull [323:28] it using this command, which is great. [323:30] So now we have the image and it is [323:31] pushed into the repo and the repo is a [323:34] public one as we mentioned before. Okay, [323:35] that's good. Clear Docker images again. [323:39] Let's push the second one, the version [323:41] two. So we're going to repeat docker [323:44] push. Now it's going to be version two. [323:47] And that's the only change. If you look [323:49] here, it's exactly the same, but this is [323:52] version two. So let me push this one. [323:55] And notice what will happen. Layer [323:57] already exists. layer already exists. [323:59] Layer already exists. So many of the [324:02] layers were in common, right? Because we [324:04] only changed the command. Everything [324:06] else is the same. And that's why the [324:08] layer exists. So it doesn't have to be [324:09] uploaded again. So now we should see two [324:13] images in Docker Hub, two versions or [324:16] two tags. [324:19] And as you can see, version two, it has [324:21] its own command. And version one, it has [324:25] its own pull command as well. And if you [324:27] look here, you'll find that there is a [324:29] digest and this is the OS architecture. [324:32] That means this is for Linux and that's [324:34] the digest. This is usually unique for [324:37] every single upload. So even if you keep [324:39] version two and now we do another push [324:41] as version two, there will be a second [324:43] and a third and a fourth digest or it [324:45] could be one for Windows, one for Linux [324:47] and so on. So there could be multiple [324:49] digests referring to the same tag. If [324:52] you want a specific one of the uploads, [324:55] then you have to use the digest and not [324:56] the tag. All right. So now we have [324:59] version one and version two, which is [325:00] great. Let's look at version two and see [325:02] if it has any changes. And as you can [325:06] see here, command is echo. This is app [325:09] one. [325:10] Let me check. Nano docker file. [325:17] So this is not showing completely in [325:19] here. Okay. Here, here it is showing [325:21] complete. All right, great. So, I have [325:23] version one, I have version two, and [325:24] life is good so far. [325:32] Now, let's go over the Docker [325:34] networking. When you create containers, [325:37] how can they communicate and how can [325:39] they communicate to the outside world [325:41] and how can they be available to [325:43] communicate with from the outside, from [325:45] external networks, from the internet. [325:47] So, this will be covered in this [325:49] section. [325:51] Let's start with an overview. Take a [325:54] step back and let's talk about a network [325:56] device called a bridge. What is a [325:58] network network bridge? This is not [326:00] about Docker. This is generally speaking [326:02] from the networking space from the [326:04] networking domain. A bridge is a data [326:07] link layer or OSI layer to physical or [326:11] virtual device. [326:13] What is the data link layer? On the OSI [326:15] layer, we have seven layers. The first [326:17] one is the cabling and electrical [326:19] signals. The second one is about the [326:22] network interfaces, the Ethernet [326:24] connectivity and so on. And then layer [326:26] three is about the IP addresses. Layer [326:28] four is about the ports and so on. So I [326:30] don't want to get into that. It is a [326:33] device that does not understand IP [326:35] addresses basically [326:37] and it can connect multiple network [326:39] segments together. So if I have PCs or [326:44] clients on segment one and I have [326:48] clients on segment two, they could be [326:49] PCs, they could be servers that this [326:52] could be the data center for example and [326:54] I would like to allow communication from [326:56] this side to this side. And when I'm [326:59] talking about segments, I'm talking [327:01] about separate networking segments [327:05] between the two. So the bridge allows [327:07] the communication from one side to the [327:09] other. So PC2 and PC3 can communicate [327:13] without issues. PC1 and PC4 can [327:16] communicate without issues. PC5 and PC6 [327:19] they can communicate without issues. [327:20] That's logically what a bridge is. [327:25] Now how does it look like? All of us we [327:29] have a form of a bridge in our homes. If [327:32] you have internet connection in your [327:34] home there will be a small device. They [327:36] call it the router sometimes. But if you [327:38] go to that device, you will see in the [327:41] back side that it has ports like this. [327:45] And the ports connect you using what we [327:47] call RG45 connectors. So these [327:50] connectors are the male connectors and [327:52] this is the female connector. It latches [327:55] inside and then the little latch here [327:58] will clip in this place and that's how [328:00] it gets fixed in in uh place. [328:04] How can a PC connect to a network device [328:06] whether it is a bridge or a switch or [328:08] even a hub? Then that cable connects on [328:11] one side to the device and on the other [328:14] side it connects in the PC or the server [328:16] or so on. So that's how connectivity [328:20] happens [328:21] and each one of these ports is called an [328:24] Ethernet port. What is Ethernet? It's a [328:26] standard protocol for OSI layer 2. You [328:30] don't need to understand more than this [328:32] for now. Just remember that Ethernet is [328:34] an interface on the network device and [328:37] an interface on the neck card or the [328:39] network interface card on the PC or the [328:42] server or the device connected to that [328:45] bridge or switch. [328:47] So this is in layman terms very basic [328:49] what a bridge is. Why did we bring this [328:52] into the discussion? Because docker [328:55] inside the host it builds software [328:57] bridges virtual bridges. Remember in [329:00] this slide we said it can be a physical [329:02] or a virtual device and that's why [329:05] docker will establish the virtual device [329:09] inside the docker host and that is a [329:12] bridge network which is a software [329:14] bridge to allow containers connected to [329:17] that bridge to communicate with one [329:19] another inside the host [329:23] by default when we start docker inside a [329:26] host a bridge network called docker zero [329:29] So a software bridge with the name [329:32] docker zero is created automatically. [329:35] So you don't have to create it. It comes [329:37] with docker by default. And any [329:40] container that will be created by [329:41] default will connect into docker zero. [329:44] And there will be a virtual Ethernet [329:47] port that will be created here on the [329:50] bridge to connect the container. We'll [329:52] discuss this in more detail as we move [329:54] forward. [329:57] So is it only a bridge that can allow [330:00] networking within a host? In Docker, we [330:03] have what we call network drivers or [330:06] network modes. So Docker network modes [330:08] include many different types of [330:11] networking that you can do inside the [330:13] Docker host and that includes bridge [330:16] which is the default network driver or [330:18] the default network mode. Then we have [330:21] host. [330:22] The host basically will have the [330:26] containers follow the host IP stack. So [330:29] they don't have their own IP addresses. [330:31] They are just as if they are extension [330:33] to the docker host. We'll talk about [330:35] that in detail as well later on. And [330:38] then we have none no networking [330:39] whatsoever. The container inside the [330:41] host cannot communicate with anything [330:43] outside cannot communicate with the [330:45] other containers and the outside or the [330:47] external networks cannot communicate to [330:49] the container. Also we will detail that. [330:52] Then we have overlay. Remember that the [330:55] bridge and the host this we are talking [330:57] about networking inside a docker host. [330:59] What if I have containers in another [331:01] host and I would like to connect the two [331:03] together. Then in that case you need the [331:06] overlay network which can connect [331:08] multiple docker demons together. This is [331:11] far from our scope so we're not going to [331:12] cover that. [331:14] Then we have IP VLAN networks which [331:16] provides full control over the IPv4 and [331:19] IPv6 addressing. [331:21] Then we have the MAC VLAN which will [331:23] assign MAC addresses to containers. [331:25] Layer 2 OSI layer 2 addresses are called [331:28] MAC addresses. This is part of Ethernet [331:30] that we mentioned. And then userdeed [331:34] building custom networks and we are [331:35] going to look at this one as well. We're [331:37] going to build custom bridge networks as [331:40] we work through the hands-on labs. All [331:42] right. Now let's dive into the docker [331:45] bridge mode. The very first one, the [331:47] default one, the docker bridge mode or [331:49] it's called the docker bridge driver. [331:53] So containers connected to the same [331:55] bridge network can communicate. So by [331:58] default you have the docker host and it [332:01] creates docker zero by default. We said [332:03] as soon as you start docker there will [332:05] be a docker zero bridge. Then containers [332:08] that you create and you leave them to [332:09] the default networking settings are [332:11] going to be on the same bridge and they [332:13] should be able to communicate with one [332:14] another. [332:16] A bridge network isolates the containers [332:19] from other containers on other bridges. [332:21] So what if I create a custom bridge, [332:23] let's say bridge one, and then I have [332:25] container three and four on bridge one. [332:27] Can the ones on docker zero and the ones [332:29] on bridge one communicate? The answer is [332:31] no. Each bridge will not allow by [332:34] default communication to the other [332:36] bridges. Bridge networks apply within [332:39] the same docker host only. What we have [332:43] now we are focused on bridge mode. [332:46] Bridge driver. So in bridge mode and [332:48] bridge driver a bridge is within the [332:50] host only cannot extend to other hosts. [332:54] A container can connect to multiple [332:56] bridge networks at the same time. And we [332:58] are going to demo that as we look into [333:02] the hands-on labs. So if I have [333:04] container two and it needs communication [333:07] with container three and container four, [333:09] I can have a second connection to the [333:11] container. So there will be a Ethernet [333:14] port or a virtual Ethernet port here [333:16] created for container 2 and there was [333:19] already one here created on docker zero [333:21] for container 2 as well. container 2 as [333:24] soon as it connects to both bridges it [333:27] will be able to communicate with one [333:29] with three and with four and we're going [333:31] to de demo that in the lab. [333:35] So let's dive a little deeper into the [333:38] networking in docker zero or the default [333:40] networking that happens on any docker [333:42] host. So the default docker bridge [333:45] network it's called docker zero and the [333:46] IP subnet the block of IP addresses from [333:49] which the containers that we create and [333:52] that will be connected to this bridge [333:54] will be assigned IP addresses is by [333:57] default 172700 [334:00] 16. So SL16 means this is the range from [334:05] which unique IP addresses will be [334:07] assigned one pair container that gets [334:10] created on the bridge or gets connected [334:12] to the bridge. All right, no worries. So [334:15] we have docker zero and we have 17270016 [334:19] as the range of or the block of IP [334:22] addresses. The very first IP address in [334:25] that block is going to be the IP default [334:27] gateway between the bridge docker zero [334:30] and the docker host. So this connection [334:32] between docker zero and the docker host [334:35] it passes by the IP address which is the [334:38] IP default gateway 17270.1 [334:42] and this does some routing function. So [334:44] it can connect discrete networks. This [334:47] is arranged different than what is on [334:49] the host. So how can they communicate? [334:52] There has to be some routing that is [334:54] happened on that gateway part of docker [334:57] zero. [334:59] When we create a container unless we [335:02] specify otherwise then every new [335:05] container will be connected to docker [335:07] zero. Any container that you create will [335:09] be connected to docker zero. But how [335:11] would that connection happen? The [335:13] connection will happen between an [335:15] Ethernet zero interface software [335:17] interface virtual that will be created [335:19] on the container and a virtual Ethernet [335:23] interface that will be created on the [335:25] bridge. And this is a logical a software [335:28] binding between the two as if it was the [335:30] cable that we were talking about in the [335:32] previous video. [335:34] Each container created in bridge mode [335:36] has an Ethernet zero as we mentioned and [335:39] the IP address gets assigned to it. So [335:42] each container gets a unique host IP [335:45] address from this range without [335:48] duplicating what we have used before. So [335:51] number one or.1 is the gateway. The very [335:54] first container created will be two. The [335:56] second will be three. The third will be [335:58] four and so on. So unique IP addresses [336:01] and we have a large pool from which we [336:03] can pick a unique unused IP address and [336:05] assign it to a new container. [336:09] And virtual Ethernet interfaces are [336:11] exactly virtual version of the physical [336:14] ports that are on the physical bridges. [336:17] So you can think of what is a virtual [336:20] interface. This is exactly as if it was [336:23] a physical one but this is in software. [336:26] So that's the meaning of a virtual [336:28] interface. An interface that cannot be [336:30] touched. It's only software and we [336:32] cannot hold it or we cannot connect a [336:35] cable into it. And this binding that [336:37] happens is also software binding between [336:40] Ethernet and the virtual Ethernet [336:42] interface that is on the bridge. So the [336:44] Ethernet gets created in the container [336:45] and the virtual Ethernet on the bridge [336:48] and the binding between the two is as if [336:51] we have a cable connected between them. [336:56] All right, that's fine. So the question [336:58] now we are still in the default bridge [337:01] mode, the default networking mode in [337:03] Docker. When I create a container and I [337:08] don't specify anything for the [337:10] networking as we mentioned there will be [337:12] an Ethernet interface an IP address from [337:14] the default range will get assigned and [337:16] a virtual Ethernet interface will be [337:18] created on the bridge and binding will [337:21] happen between the two. All right. So [337:24] the question is if I have external [337:26] networks the host can reach these [337:28] external networks. Let's say these are [337:29] on the internet websites or whatever on [337:31] the internet. Would the container in the [337:35] default bridge mode be able to access [337:38] the external sites? So for example, [337:41] would the container be a able to ping [337:44] the 8.8.8.8 [337:47] IP address which is the Google DNS. [337:50] Would it be able to do this? If the host [337:52] can do it, would the container be able [337:55] to do it? And the answer is absolutely [337:57] yes. Outbound connectivity. We call this [337:59] outbound. Outbound means it's coming [338:01] from here initiated and it's going out [338:05] to the external networks. So it's going [338:07] out of the container. It reaches the [338:09] host through the IP gateway gets to the [338:13] interface Ethernet zero of the docker [338:15] host and then it will route it outside. [338:18] Now the question is if this is on the [338:21] internet but this is a private IP [338:24] address. a private IP address cannot be [338:26] seen on the internet. Then how can this [338:28] be masked such that the internet will [338:32] see that this is coming from somewhere [338:34] on the internet and then when the [338:36] response comes back then this will be [338:38] reversed again and it will be sent to [338:41] the right container and the answer is [338:44] network address translation. [338:47] the host will perform network address [338:49] translation as that traffic is coming [338:52] out and when the response comes back and [338:56] it looks like this. So let's say the [338:59] docker container would like to [339:01] communicate with the outside 8.8.8.8. [339:04] So the packet or the message is going to [339:07] be sent out and the source is [339:09] 172.17.0.2. [339:11] This is the sender [339:13] and the destination is 8.8.8 8.8 [339:18] as it travels through docker zero and [339:20] the IP gateway and it gets to the host [339:23] the docker docker software itself will [339:26] find out okay hold on hold on this is [339:29] going to the internet and it is going [339:31] out of my controlled area which is the [339:34] docker controlled area [339:36] the IP addresses here are private and [339:39] they are not known to the outside so [339:41] what I need to do is I need to strip the [339:44] source IP address from the message and [339:48] I'm going to add of course it works with [339:50] the host on this and it's going to add [339:53] the IP address of the host as if the [339:56] message is actually coming out from the [339:58] host and now if this is a private IP [340:02] address then the host or the network [340:04] that the host is connected to if this is [340:07] AWS cloud the AWS cloud is going to also [340:10] do network address translation and hide [340:13] that behind the public IP address [340:15] reachable from the internet. So the [340:18] docker host is going to translate that [340:21] the message was from this source. It [340:23] would now assume or the message that [340:26] will come out of the host will have a [340:28] source address that is the host IP [340:31] address. So the source address will be [340:33] the host IP address. When the traffic [340:36] comes back the source will be 8.8.8.8 8 [340:40] and the destination will be the IP [340:43] address of the host. So when it comes [340:46] back then the host will realize who [340:49] talked to 8.8.8.8 [340:51] and it will find out this was the [340:53] container and that's how the destination [340:56] will be changed from this IP address to [341:00] the container IP address. Okay. So [341:02] that's called network address [341:04] translation and the docker host will [341:06] maintain the net entries in IP tables. [341:10] Okay. So if you want to think about [341:12] that, if you don't have an idea about [341:13] it, let's say that my name is Issa and [341:16] there is and your name is George and I [341:18] would like to talk to you. However, I'm [341:20] not allowed to talk to you directly [341:22] because I have a functionality or a [341:26] function inside that office and I should [341:28] not be able to talk to the client [341:30] directly. But there is a mediator called [341:33] Joan and Joan can talk to George and can [341:36] talk to me. So if I need to talk to you [341:40] George, I'm going to talk to John. John, [341:42] can you please get this message [341:45] to George? So we have here Issa [341:49] and we have John and we have George. [341:53] Issa would like to talk to George [341:55] directly but this is not possible. So [341:57] what Issa will do is Issa is going to [342:00] give the message the envelope if you [342:02] will to John and would say John this is [342:06] going to George. So what John will do [342:09] because we don't want anyone to know [342:11] that Issa is speaking to George and they [342:14] are not allowed to speak to each other [342:16] directly. So what we'll do is John now [342:18] is going to change the envelope and [342:20] we'll write on the outside that this is [342:23] coming from John where in fact this was [342:26] coming from Issa not from John and it [342:28] was going to George through Joan now it [342:31] will be from Joan to George that's [342:34] exactly what happens but Joan because [342:36] he's doing the same to Isa and to Ahmed [342:38] and to Ram and to other people John is [342:41] going to maintain a table and would say [342:45] okay I know that Issa [342:47] was talking to George and maybe Ahmed [342:51] was talking to Ram [342:53] and then maybe Krishna was talking to [342:57] Sara. So he will maintain this table. [343:00] Now when the response comes back from [343:03] George [343:05] doesn't know about Asa. So what will [343:07] George do? He will say okay here is the [343:10] response John. So we'll give John the [343:13] response. John is going to look at this [343:15] table and would say who was speaking to [343:17] George? Oh, that was Issa. So, it will [343:20] send the response back to Issa. So, [343:23] that's exactly what happens, but instead [343:25] of names, these are IP addresses. [343:28] All right. Hopefully, this is clear and [343:30] we are going to look at that in the [343:31] table. [343:34] Now, bridge mode. Can I have multiple [343:36] bridge networks inside a Docker host? [343:39] And the answer is yes, absolutely. We [343:42] have the userdefined or the custom [343:44] networks and you can build your own if [343:46] you would like to. So they can coexist [343:48] inside a docker host. But of course [343:50] there has to be a reason for that. It's [343:52] not just creating networks to be cool. [343:55] So by default let's say we have app one [343:57] containers and they are going to be on [344:00] docker zero. Here is the range and this [344:02] is the IP address assigned to the [344:04] container and this is the bridge gateway [344:07] or the IP gateway.1. [344:10] and this is the Ethernet and this is the [344:11] IP address of the docker host and the [344:13] docker host is connected to the external [344:15] networks. Now if I bring in another [344:18] network then there will be a new bridge [344:21] different bridge and then containers [344:23] connected to that bridge are going to [344:25] also have a different range and they [344:28] will have different IP addresses. So if [344:29] this was for a database or application 2 [344:31] or anything and we created a custom [344:34] network bridge one for example when you [344:38] create a custom network it will not get [344:40] the same default range it will get an [344:42] other range and you can specify a range [344:45] other than the 172 if you would like to. [344:48] So it can be 10.0 and we'll see that in [344:50] the lab. [344:52] Now you connect the containers and [344:55] virtual interfaces will be connected on [344:57] bridge zero for the containers that will [344:59] be attached by default to docker zero. [345:02] And if you specify for app to container [345:05] that you need to connect to bridge one [345:07] when you are creating it then it will [345:09] get an IP address but from a different [345:11] range which is the range of bridge one. [345:14] So this is possible and containers are [345:16] going to have outbound access and also [345:19] Ethernet zero or the host is going to [345:22] maintain a table of who is talking to [345:24] whom. So when the response comes back [345:27] then the translation of addresses can [345:29] happen without any problems. [345:31] So we can create custom bridge networks [345:33] as needed aside from the default bridge. [345:36] So this one will be created anyways as [345:38] soon as we start Docker but you can [345:40] build others other networks if you'd [345:42] like to. Please remember that by default [345:46] bridges isolate their containers from [345:49] all other containers. They cannot [345:51] communicate. So this one and this one by [345:53] default they will not be able to [345:54] communicate. So let's now cover some of [345:57] the docker networking commands that will [345:58] come in handy when you are dealing with [346:00] docker networking. A Linux command at [346:03] the beginning is very crucial which is [346:05] the IP address command or the IPA. The [346:08] very first command we are going to use [346:09] is IPA. very important command that we [346:12] use on the host and inside the container [346:14] when we are inside a shell in the [346:16] container to find out information about [346:18] the available network interfaces and if [346:20] they have associated IP addresses on a [346:23] Linuxbased system [346:26] if this utility is not available in your [346:28] container you can install it using the [346:30] IP route 2 utility and we will see that [346:33] in the lab now what if I need to find [346:36] out on my docker host what are the [346:38] available networks docker networks So I [346:40] can use docker networks ls and that will [346:43] list all the available docker networks [346:47] docker networks create and then the name [346:51] this is if you would like to create a [346:53] custom network in docker so this was [346:55] going to create a network with a [346:57] specific name if you did not specify the [347:00] subnet or the IP range then it's going [347:02] to to take the next available 172 range [347:07] if this was the first custom network, it [347:10] will take the 172.18. If it was the [347:13] second one, it will take 172.19 and so [347:16] on. [347:18] What if I don't want a default IP subnet [347:20] range for the network and I would like [347:22] to specify my own? Then you can do [347:24] docker network create hyphen subnet and [347:28] then the subnet range you would like to [347:29] use and then the name of the custom [347:32] network. What if I need to inspect one [347:35] of the networks and I would like to find [347:37] out which containers are on this network [347:40] and what are the IP addresses they are [347:42] assigned to, what's the range of the [347:44] network and so on. So a lot of details [347:46] about one of the networks whether it is [347:48] docker zero or one of the custom [347:50] networks then you can use the command [347:53] docker network inspect not docker [347:56] inspect network docker network inspect [347:59] and the name of the network or the ID of [348:01] the network. [348:06] If you want to create a container using [348:09] docker run, but you would like this [348:12] container not to be connected to the [348:14] default docker bridge which is docker [348:17] zero. You want it to be connected to [348:19] bridge one or application such and such [348:23] network. Then you can when you are [348:25] creating the docker run you can use [348:27] hyphen network and the name of the [348:30] network and then the image. And of [348:32] course you can combine that with hyphen [348:34] it and hyphen d and hyphen all the [348:36] hyphens that we have seen before and the [348:38] hyphen p to publish ports and so on. So [348:41] this will run a new container and [348:43] connect it to a docker network that you [348:45] have specified here. You can also do for [348:50] an existing container that is not [348:52] connected to a custom network. So let's [348:54] say I created a container. The container [348:56] by default is in docker zero. Later on [348:58] we created a new network. Let's say it's [349:01] called bridge one. And now I would like [349:04] to connect that container that was only [349:06] connected to docker zero to also have a [349:09] connection into bridge one. What do I [349:11] do? In that case you can do docker [349:13] network connect the name of the network [349:16] and then the name of the container. The [349:17] network is first and then the container [349:20] comes second. Not the other way around. [349:23] So we did the testing we wanted and for [349:25] whatever reason now I need to disconnect [349:28] the container from bridge one again. [349:30] Then you can use the command docker [349:32] network disconnect the name of the [349:35] network and the container name or the [349:37] container ID. All right. So now let's [349:40] look at the bridge mode in the docker [349:42] networking modes or networking drivers. [349:45] Let's go ahead and look at that. So I [349:48] have the docker host and it's running [349:49] right now. So I'm going to do connect [349:51] and I'm going to open two terminals as [349:53] we are used to. [349:56] So again connect and again another [349:59] terminal [350:01] and then in each one of them I'm going [350:03] to do the normal sudo su and then clear. [350:07] So now we are inside the host as the [350:10] root in terms of privileges [350:13] and clear again. So what I need to do is [350:16] I need to create a container and I need [350:20] to get into that container and check [350:22] outbound connectivity. Does a container [350:25] by default has outbound access to the [350:28] internet? And the reason why the [350:30] container has access to the internet is [350:32] because the docker host the EC2 instance [350:36] has public IP address and it is launched [350:39] on a public subnet. So it can access the [350:42] internet. So if the host can access the [350:44] internet, can the container access the [350:45] internet? That's what we'll investigate [350:47] right now. [350:50] Let's do docker images. And this image I [350:54] created from Ubuntu and it does have the [350:56] utilities installed. Usually the Ubuntu [350:58] does not have the curl and ping and IPA [351:00] and all that. So this one has it. So I'm [351:03] going to launch a container from this [351:05] image docker run. And I'm going to do [351:08] minus it. I need to get into the [351:10] container and I'm going to assign the [351:12] name p test and it is from this [351:17] image [351:20] and the version is 1.1 and I'm going to [351:22] run bash. So now I'm inside the [351:25] container. Here's the container ID. If I [351:28] do [351:32] pwd I am at the root and what I will do [351:36] right now is I want to do ping [351:41] 8.8.8.8 [351:43] which is the Google DNS. As you can see [351:45] we are getting a response which means [351:49] the container [351:51] has access to the outside world. [351:54] Remember that the container will have an [351:56] IP address. Let's investigate that. [352:00] So let's do IPA or IP address. [352:04] So we did IP address or IPA. If you do [352:06] IPA, you'll get exactly the same output. [352:09] So what is the output? Here's the [352:10] command. Let's look at what is this. [352:13] This is the loop back interface. So any [352:15] container whether it has connectivity [352:17] and in networking or not will have a [352:18] loop back interface an internal [352:21] interface. Don't worry about that. The [352:23] most important one is this one Ethernet [352:25] zero. Remember we said that any [352:28] container that is established or created [352:30] will have an Ethernet interface and it's [352:33] always in Ethernet zero for the first [352:34] one. The second one will be Ethernet one [352:36] and so on. So look here what do we see [352:39] here? We see that it had received [352:43] an IP address 172.17.0.216. [352:47] Remember when we were talking about the [352:50] fact that the range by default for the [352:52] docker bridge is 1727006 [352:56] and.1 is the IP gateway. This is now the [352:59] container and that's the IP address that [353:01] it has and this is Ethernet zero as we [353:04] mentioned. So this is on so this is on [353:08] the container. What is going on on the [353:11] other side which is the host? Let's [353:13] check. Let's do IPA. [353:17] And if you look here, we have the loop [353:19] back as well. Then we have this one [353:23] which is from AWS. And that's the [353:25] private IP address of the virtual [353:28] instance, the Docker host or the EC2 [353:30] instance. How do I know this? If you [353:33] look at this number and you look at this [353:35] number, it's exactly the same. [353:37] 1723145181 [353:39] and it's exactly the same. So this is [353:41] the private IP address of the Docker [353:45] host. Right now again what else do we [353:48] see? We see docker zero. So docker zero [353:52] is the default bridge. [353:57] And for docker zero here what we have is [353:59] we have an inter internet interface [354:02] 1727016. [354:04] Remember what that was? This exactly [354:07] this was the the IP gateway of the [354:09] docker bridge. So the interface docker [354:12] zero is on the default bridge and the [354:15] default bridge is docker zero and it has [354:18] an IP gateway or an IP address interface [354:21] and it has an IP address and that's how [354:24] the host communicates with the docker [354:28] engine or the docker uh bridge. Then we [354:32] have virtual Ethernet. Remember when we [354:34] said that every container that you [354:37] create will have Ethernet zero on the [354:39] container side and will have a virtual [354:42] Ethernet interface on the bridge side. [354:45] So this is V8 or V virtual Ethernet 8. [354:49] It's up and it is on docker zero. So it [354:52] is on the bridge. So this proves that it [354:54] is on the bridge. And this is [354:57] the IPv6 interface. The inet 6 is for [355:01] IPv6. So you're not only getting an IPv4 [355:04] but there is an IPv6 also or the subnet [355:07] scope link that is available on the [355:10] bridge side. So now you have all of this [355:13] which proves what we have said in the [355:15] theory and that is how the container was [355:18] able to access the outbound. Now how can [355:21] we confirm that this belongs or this is [355:23] connected to the container? Very easy. [355:26] Let's go here and let me do exit. And [355:29] when I do exit, let me do docker ps. [355:33] There are no active containers. ps minus [355:36] a. I will find the container that we [355:38] have created. Here is the name and it is [355:40] exited. Now let's go ahead here again [355:43] and let me repeat repeat the same [355:45] command. You will not find the virtual [355:48] ethernet. So I have the one which is the [355:50] private IP from AWS. I have the docker [355:52] zero did not change but I don't have the [355:54] virtual Ethernet. So with virtual [355:56] Ethernet interfaces on the bridge side [355:58] they are created and terminated. When [356:00] you create the container they are [356:01] created. When they are terminate the [356:03] container or exit the container they are [356:05] exited as well or they are terminated as [356:07] well. All right. So let's now clear and [356:10] let me do the so let's do the bridge [356:13] mode in docker networking and let's do a [356:16] deep dive. So let's do docker network ls [356:19] list the existing networks and look at [356:22] what we will see now. So I did not [356:24] create anyone. These are all defaults. [356:27] So I have this network ID. The name is [356:30] bridge and the driver is bridge and it [356:34] is local. [356:35] Then I have this one and the type or the [356:38] name is host. The driver is host. So it [356:41] is from the docker networking host type [356:44] and it is local. And then we have none [356:47] and the driver is null and that's local. [356:50] So I have three networks available on [356:52] the docker host by default. That's what [356:54] we have right now. All right. So let me [356:56] do a clear now. [356:59] And what we will do now is let's create [357:00] a container. Docker run fy- [357:05] it. The name is container one. The image [357:09] is engine x. [357:11] And I'm going to run [357:14] a shell inside. And I have the [357:16] interactive [357:18] /bin /bash and I have the interactive [357:22] here. So this will keep the container up [357:26] and running. So I'm inside the container [357:29] right now. As you can see, if I do IPA, [357:33] you'll find that the command is not [357:34] found. So what do we do if you wanted to [357:36] install this? If I want to confirm [357:38] whether it exists or not, if I want to [357:41] confirm, I will do IP address. Do I have [357:44] this? If you don't get any response that [357:46] means engine X by default it doesn't [357:49] have the IPA address. Okay. So let me do [357:52] ping 8.8.8.8 [357:54] again command is not found which ping. [357:57] So do you have it installed? No I don't [357:59] have it. If you want to confirm then [358:02] let's do ls and you'll find that ls [358:05] exists and here is the path. So the [358:08] packages or the tools or the commands [358:09] that are available on the image you will [358:12] find that it will respond with a path. [358:14] If it doesn't exist then it will be just [358:17] quite silent. So what do I do now? You [358:20] can do apt get update. [358:26] So now I'm updating the image and then I [358:28] will do apt [358:30] get install minus y. If you want the [358:33] ping then it is IP utils/ping. [358:40] And now it will install ping. Now let's [358:43] clear and let me do ping 8.8.8.8. You'll [358:47] find that it is responding now. So it [358:49] has been installed. And if I do which [358:52] ping you'll find that there is a path to [358:54] it. So now it is installed. So don't be [358:57] afraid or panic when you don't when you [359:00] try to do these commands and they don't [359:01] exist. That means the package is not [359:03] installed. That's all. [359:08] If I do IP address now it's not [359:11] available. So what I will do is app get [359:13] install minus Y and then I will do IP [359:17] root 2 and this will install many things [359:21] including IPA. So if I do IPA now you'll [359:24] find that the response is not it's not [359:26] found. It's it is found now and it has [359:29] responded. And if I do which IP address [359:33] then it will tell me that there is a [359:35] path to it. All right. So I have it [359:37] available now. [359:41] So we have an IP address on the [359:43] container. Notice that since we stopped [359:45] the first container now the second one [359:47] we created it took the same or the first [359:49] available IP address which is2. That [359:52] means a stopped container kind of loses [359:55] its IP address. Okay. So let me go on [359:59] the other terminal. I'll keep this one [360:00] up and running and I will go on the [360:02] other one and I'm going to do docker [360:04] network inspect. I want to inspect the [360:06] network [360:08] that is with this ID the bridge one. [360:16] Let's look at what information we have [360:19] when we do this. So the name is bridge [360:21] and here is an ID and it has been [360:24] created on such and such date. The [360:26] driver is bridge. So it tells you what [360:28] the mode is. [360:30] Then here is the subnet for the [360:32] configuration. This is the subnet. These [360:35] are all defaults. So it confirms what we [360:37] said before. And this is the IP gateway. [360:42] Then [360:45] we have here as you can say containers. [360:48] I have one container running with the [360:50] name cont one container one and the MAC [360:54] address the layer 2 address and the IP [360:56] address are available here as well [361:01] and it is docker zero. So got so we get [361:05] a lot of information about the network [361:07] and its details and also the running [361:09] containers. So let's do this. Let me [361:11] just go here and do exit. So when I do [361:14] exit what will happen? Yes, the [361:16] container will stop. So docker ps minus [361:18] a I have two containers stopped and [361:21] container one is included as well. Now [361:23] if I go back here and I run the same [361:25] command again [361:27] and we get the output you'll find that [361:30] now so if we inspect the network again [361:34] you'll find that we don't have any [361:36] containers available. It might take a [361:38] couple of seconds between the time you [361:40] stop the container and the IP address to [361:42] be revoked but now I don't have any [361:44] running containers as you see here. [361:53] When we create an application that is [361:55] going to have containers, that [361:58] application is going to have data. So it [362:00] could be files that the application is [362:02] going to create. It could be that [362:04] database or the data in a database if [362:06] that container was about a database. So [362:08] how can we keep that? How can we [362:10] maintain it even if we restart the [362:13] container or we kill the container or we [362:15] delete the container? That data could be [362:18] critical and we would like to maintain [362:20] it. And that is what is data persistence [362:23] all about. How can I make sure that my [362:26] data is going to survive a container [362:30] delete or a container hang or any issues [362:33] with a container? That is what we are [362:35] going to discuss in this section. So why [362:38] do we need to persist the data in [362:40] Docker? As I just mentioned, because if [362:42] you have a container with data and the [362:46] container is deleted or is killed or it [362:49] stops or whatever the problem happens [362:51] with the container, I'm going to lose my [362:53] data. Think of a MySQL database for [362:56] example or critical data files or [363:00] information or session data even that [363:02] you are using and then the container [363:04] disappears all of a sudden and all the [363:06] data is gone. How can you recover it? [363:09] That is what we are going to discuss [363:11] now. The benefits of persisting data in [363:14] Docker are many and the least is [363:19] database files logs and all that we [363:21] would like to maintain them. That's the [363:22] number one benefit. And then we can also [363:24] share data between containers. Let's say [363:26] it is the website data, the index.html [363:30] and the other HTML files. Now if I run a [363:32] container, it will tap into these files. [363:35] If I run 10 containers, I don't want [363:37] each of them to have a copy of that on [363:39] itself. Why don't they access a common [363:42] or shared data in a volume or in a [363:45] storage that is independent of the [363:48] container itself? [363:52] Also we can use it to separate [363:54] application code from user data. So we [363:56] don't have to store the database data [363:59] for example on the container with the [364:02] database engine itself or if it is an [364:04] application related data I don't want it [364:06] to be with the code on the same [364:07] container. Avoid losing data when a [364:10] container stops or is deleted. [364:14] There are two common ways to persist [364:17] data in docker. The first one is called [364:19] named Docker volumes or they could be [364:21] anonymous docker volumes. So docker will [364:24] create random names for the volumes. [364:27] That is one thing. And then the other [364:29] way is we can have folders on the host [364:32] and these are going to be where the [364:34] containers are going to save their data [364:37] and they are called bind mounts or bind [364:39] mounting. The difference between the two [364:41] is when you create Docker volumes or [364:43] name Docker volumes, they're going to be [364:45] on directories in the host in an area on [364:49] the host that is completely controlled [364:51] by Docker. [364:53] Bind mounts. They are folders or [364:56] directories on the Docker host, but they [364:58] are not controlled by Docker. They are [365:00] on the host file system. So, this is the [365:03] main difference and we're going to look [365:04] at them and when to use each. Let's now [365:07] discuss the first type of persisting [365:10] data solutions in docker which is the [365:13] named docker volumes or sometimes called [365:15] the docker volumes. [365:18] Volumes are going to be in the host file [365:20] system. So if this is the docker host [365:22] the green rectangle in the host file [365:25] system there is an area controlled by [365:28] docker and the volume when we do the [365:31] named volumes storage to persist data [365:35] then it's going to be somewhere in the [365:37] docker area. [365:42] So where in the docker area where in the [365:45] file system as we mentioned early on [365:47] that if you have a normal installation [365:49] default installation path for docker on [365:52] Linux system or Mac OS not on a virtual [365:55] machine on Windows or your laptop then [365:58] the default path is going to be [366:00] v/b/doccker [366:02] and then we will have a directory called [366:05] volumes and this will be the volume [366:07] name. So this is let's say you create a [366:09] volume called volume one this is going [366:11] to be volume one folder and then [366:13] underscore data and anything that has to [366:16] do with this volume is going to be [366:17] stored under this subfolder. [366:21] So if I have multiple volumes they will [366:23] share this common start path and then it [366:26] will be volume one volume 2 volume 3 [366:28] demo volume data volume and so on. And [366:31] as this shows that when we have a volume [366:34] that we are going to mount with a [366:35] container, the storage in that volume [366:38] path is going to be into the storage [366:41] volume on the host. So even if we lose [366:44] the container, the data is going to be [366:46] in a volume on the host, not in the [366:49] container itself. And here's the path [366:52] var docker volumes. And then the name of [366:55] the volume, the volume name and [366:57] underscore data. And we can have [366:59] multiple containers mount that volume. [367:02] It's not a single container volume. [367:07] The Docker volume is isolated from [367:09] container layers. So when you write to [367:11] it, you're not writing to the file [367:13] system of the container. It will persist [367:17] independent of the container. So even if [367:19] the container is deleted, the data is [367:21] still there because it's on the host. [367:23] And it is mounted into containers at run [367:26] time, not after. [367:28] And it allows data to survive container [367:30] restarts, deletions, and image rebuilds. [367:33] All of that the data is going to be on [367:35] the host. But of course, if you lose the [367:37] host, then you have a problem because [367:39] the host will take out all the [367:41] containers and all the volumes and all [367:44] the data in the volumes as well. We are [367:46] still talking about Docker in a single [367:48] host. We did not get into the swarm [367:50] docker swarm part where we can [367:52] orchestrate or can create containers on [367:54] multiple hosts. [367:59] Docker volume commands. How can I use [368:01] commands to create and to mount Docker [368:03] volumes and so on? So if you want to [368:06] create a named Docker volume, you can do [368:08] Docker volume create and the volume name [368:12] that you specify or that you prefer to [368:14] have. [368:16] You can list the available Docker [368:18] volumes using the Docker volume ls [368:20] command. And you can inspect and get a [368:23] lot more details about a docker volume [368:25] when you do the docker volume inspect [368:27] and the volume name. [368:30] And you can also delete a docker volume [368:32] using the rm or remove and a volume [368:34] name. So docker volume remove or rm [368:41] when you want to mount an existing [368:44] docker volume when you are creating a [368:46] container using the docker run command. [368:48] How can you do it? This is what we are [368:50] going to look at right now. So the [368:52] option in the docker run command that [368:54] you can use to mount a volume is hyphen [368:56] v and then you have the volume name that [369:00] you have created column and then the [369:03] path or the directory in the container [369:06] where that volume is going to be [369:07] mounted. So this is to launch a [369:10] container with a volume attached. But of [369:12] course you need to have the docker run [369:13] command before that. Here's an example. [369:16] docker run minus v hyphen v my data. So [369:21] we have a volume with the name my data [369:24] and it's going to be mounted at the app [369:27] data directory in the container and the [369:30] image is Ubuntu. So inside the container [369:32] if I go into the app data folder and I [369:35] write anything or save anything this is [369:38] going to be in the volume that is on the [369:40] docker host. It's not going to be in the [369:43] container file system. So you are [369:45] writing as if it is in the containeriz [369:47] file system but that goes automatically [369:49] into the volume on the docker host. [369:56] We can also provide a read only access [370:00] for a container to a volume. So if I do [370:02] the docker run hyphen v the volume name [370:04] and the container path and colon ro that [370:09] means read only. So give the container [370:10] read only access to this volume. It [370:13] cannot save files and it cannot edit [370:14] what is on the volume. And here's an [370:17] example. Docker run-v [370:20] my data. So this is the name of the [370:22] volume and the path inside the container [370:24] is app/d data and then it is read only [370:27] from an Ubuntu image. [370:33] We can share or have multiple containers [370:36] use the same Docker volume. And it's up [370:38] to you where you want to mount the [370:40] volume inside the file system in each [370:42] container. [370:44] So more than one container can share the [370:46] same volume and they can have access to [370:48] the data in the volume. If you have a [370:50] container and you'd like the container [370:52] to inherit or have all the mounting all [370:55] the volumes that are in another [370:56] container, you can also use it with a [370:58] docker run hyphen volumes from flag [371:03] which will allow one container that you [371:05] are creating to have all the volume [371:07] mounts from another container. It's not [371:09] as common to use. However, it's a [371:12] feature that's available. So if you do [371:14] volumes from container one that means [371:17] the new container is going to take that [371:21] volume mounts from container one into [371:23] container 2. So this is going to be [371:25] preceded with docker run and the name of [371:28] the container is container 2 and then [371:30] hyphen hyphen volumes from container [371:32] one. So you're not specifying the single [371:35] volume mount. You are mounting whatever [371:38] is on container one in container two. [371:42] And here's a full example docker run [371:45] interactive uh session hyphen volumes [371:48] from container one Ubuntu. [371:51] So this is going to have that the it or [371:53] you can hear run bash for example. This [371:55] is not showing here. So you can get into [371:58] that container command line but also [372:00] you'll get all the volumes from [372:03] container main. Let's go ahead and play [372:05] with the named Docker volumes. The first [372:07] type of persisting data in Docker. So, [372:11] let's open two sessions to the Docker [372:14] host as we always do. [372:19] I'm going to open a second one. Connect. [372:23] And then connect. [372:26] I'm going to do sudo su and clear. [372:32] And here I'll do the same. [372:37] Okay. So, what do we need to do now? I [372:39] need to create a docker volume and then [372:42] we are going to create a container and [372:44] mount this volume to it and then we are [372:47] going to get into the container write [372:51] some text using a echo command into a [372:55] file and then we are going to exit from [372:58] the container the container will be [373:00] removed I'm going to use the docker run [373:02] hyphen rm which means as soon as you [373:06] exit from the container from the [373:07] interactive shell it The container is [373:09] going to be deleted completely deleted. [373:11] So it will not even show in the docker [373:13] ps minus a. [373:17] And after doing this we are going to [373:18] create another container and then we are [373:21] going to mount the same volume to it. [373:22] And then we are going to ls get inside [373:25] the container and find out if we have [373:26] the same data available or not. Then the [373:29] second container also would be created [373:31] with a minus minus or hyphen rm which [373:34] means remove as soon as it's exited. [373:37] We'll exit from the second container and [373:39] then we're going to do a cat to the path [373:42] in the docker area where the volume is [373:45] and see if we have that data or not. So [373:48] that's what we are going to do right [373:49] now. And this will prove despite the [373:52] fact that the first container was [373:53] deleted when we launched the second [373:55] container and mounted the same volume [373:57] the data was still there which means it [373:59] is not in the container that was [374:00] deleted. And when the second container [374:03] gets deleted, we do the cat to the path [374:06] in the host and we'll still find that [374:08] the data is there, which means the data [374:11] persist irrespective of the life of the [374:13] containers. So let's go ahead and do [374:15] this. Okay, so here's what we're going [374:17] to do. Let's go ahead and check if we [374:19] have any Docker volumes available [374:21] beforehand. [374:24] And we don't have any. Let's go ahead [374:26] and create our first named Docker [374:28] volume. So, docker volume create [374:33] and I'm going to call it volume one. [374:38] If we do the same command ls again, it [374:40] should show me volume one. I can do [374:43] docker inspect volume one. [374:47] And as you can see when it was created [374:48] and it's local and here is the mount [374:51] point where this volume is mounted and [374:53] the name is volume one. I'm going to [374:56] look at this path because it's very [374:57] important. /bar /bdoccker this is the [375:01] docker controlled area it has a [375:03] subdirectory called volumes and I have a [375:05] volume called volume one under that and [375:07] then a subdirectory underscore data and [375:10] then any data I'm going to save in that [375:12] volume from the container it's going to [375:15] happen under the /data subdirectory so [375:17] I'm going to copy this because I'm going [375:19] to use it shortly all right let me clear [375:24] okay let's go ahead now and run a [375:26] container [375:28] And this will be used docker run and [375:30] then minus rm or minus minus rm. Delete [375:33] the container as soon as it job is [375:35] finished or as soon as you exit from the [375:37] container. And then I need to mount the [375:39] volume [375:41] one and this will be mounted at the / [375:45] data directory on the container. I'm [375:48] going to create it from an Ubuntu image [375:50] and I'm going to execute the command or [375:52] this is the command that the container [375:54] will execute. bash minus C treat [375:56] anything between the strings as a [375:58] command echo [376:00] and then I'm going to echo hello from [376:04] docker [376:06] volumes [376:09] and this will be redirected under data [376:11] under a file called hello.ext. [376:14] So basically create a file called [376:17] hello.ext text under the folder data [376:19] which means it will be created on the [376:21] volume if what we are saying is true and [376:24] the container will execute this and the [376:26] content of the hello text will be this [376:27] text and that is going to be under the [376:30] SL data directory which means it will be [376:32] in volume one so let's go ahead and do [376:34] this and find out what's going on I did [376:37] not close the code [376:39] so let me repeat the command again and [376:42] let's close the code because we have a [376:45] quote here it has to close and and let [376:47] me hit enter now. All right. So let's do [376:50] docker ps minus a. I don't see any [376:53] containers because this instructs to [376:56] delete the container. So the best way to [376:58] find out is if we cat and then var li do [377:04] docker volumes volume one data and [377:09] hello.ext. [377:13] So this confirms that this file has been [377:15] created. [377:17] under var lib docker which is the docker [377:19] storage area and then volumes volume one [377:23] data and there is a file and how do I [377:25] know because here is the output which is [377:28] exactly what we have instructed it to do [377:30] right here okay so the container [377:33] disappeared deleted but the data is [377:35] still there now can I use that on a [377:38] different container let's find out [377:41] so let me repeat the long command again [377:43] but we don't need all of is [377:49] right. So I'm going to go here and I'm [377:52] going to get into the container /it [377:56] and it's going to be a bash and created [377:59] from Ubuntu. So now I'm inside the [378:00] container. Let's do ls and I have a data [378:04] folder here as you can see. So let's see [378:06] let's do cd data and ls. I have the [378:10] hello.ext text which was from the [378:12] previous container made by the previous [378:14] container but the container is gone but [378:16] the data persisted the data is still [378:18] there and if I do get kh hello text this [378:22] proves that the volumes persist [378:25] even if the container is completely [378:28] deleted [378:30] right I think it's clear and let's go [378:33] ahead and now extend this and look at [378:37] volumes when two containers are live and [378:39] they are saving files and what happens [378:41] on the other container. So let's go [378:42] ahead and do this right now. So let me [378:44] exit from this one. [378:47] If I do docker ps, I shouldn't see any [378:49] because we used a hyphen rm and I don't [378:52] have any. And I am done with the volume. [378:56] So let's go ahead and also remove volume [378:59] one. [379:01] And if I do docker volumes ls, I [379:05] shouldn't see any. Okay, let's clear. [379:07] Now what do we need to do? I need to [379:09] create two containers [379:11] and I'm going to mount the same volume [379:14] volume two on both containers and I'm [379:16] going to get into one container create a [379:19] file on that directory for the volume [379:22] and then get into the second one and [379:25] check if I can see that file from [379:27] container one. Then I will create a file [379:30] from container two and then go to [379:31] container one and see if it can see that [379:33] file or not. So by doing this that means [379:37] visibility of the data shared in the [379:39] volume is going to be across the [379:41] containers that have this volume mounted [379:43] onto them and they will have read and [379:46] write access to the volume unless if I [379:48] choose to provide them only read only [379:50] access and this is what we are going to [379:53] end the lab with a third container with [379:56] readon access to the volume. All right. [379:58] So, I'm going to do docker volume create [380:02] and I'm going to create volume 2 this [380:04] time. And if I do docker volume [380:08] ls, [380:10] I have it. And do docker volume [380:13] inspect [380:15] volume 2. And here is my volume. That's [380:19] all good right now. Okay. Let me clear. [380:22] And I'm going to create now container [380:24] one on this side. So, docker run hyphen [380:28] it I want to have interactive shell into [380:30] the container and I'm going to have [380:33] volume 2 mounted into the let's say [380:36] folder one inside the first container [380:40] and this is going to be an Ubuntu [380:41] container and I'm going to run a bash [380:44] shell into it. So now we are into the [380:47] first container. Let me go to the other [380:50] side and I'm going to use the same [380:53] command but let's do folder two on this [380:57] container [381:01] and I'm now inside the second container. [381:04] Let me do [381:05] ls and you'll find folder two here. So [381:09] if I want to save anything to the volume [381:11] I need to write it to folder two. So [381:13] let's move into [381:15] folder 2 [381:17] and do all my work here. So I'm going to [381:20] echo [381:22] hello from container 2. [381:26] And I'm going to redirect that to [381:29] container2.ext [381:31] ls. And if I c the file cont 2.ext, I [381:35] should see what I have just typed. All [381:37] right. So let's take this command now. [381:40] And I'm going to go to the first [381:42] container and I'm going to do the same [381:45] thing. LS and I have here folder one. [381:48] I'm going to go into folder one and I'm [381:51] going to use this command but I'm going [381:53] to to say this is container one.ext and [381:56] hello from container one. [382:00] And if I do ls as you can see I have [382:03] access to container 2 file and container [382:06] one file. How? because you are writing [382:09] in the folder that maps to the volume. [382:10] So everything you are actually saving [382:12] goes into the volume and that data will [382:15] persist even if the two containers are [382:17] gone. So let's cat from here count2.ext [382:21] to check and yes that's true. And if I [382:25] cat one text [382:29] now if I go in the other one and I do ls [382:31] again now I can see two files. So read [382:35] write access to both of them. Now let's [382:38] do one thing. Let me open a third [382:40] terminal [382:43] and I need to inspect these containers [382:46] and find out the mount path if they have [382:48] any reference to the volume attached to [382:50] them and where it is mounted. So I'm [382:53] going to do sudo su [382:56] clear. Let's do docker ps minus a. [383:02] So I have these two containers. I would [383:04] like to inspect each one of them. [383:07] So, I'm going to do docker inspect [383:10] for the first container. [383:13] And if we go up [383:17] until we found the mounts [383:22] here, mounts, you'll find that there is [383:25] a volume mounted. The name is volume 2. [383:28] And here is the source or the path to [383:30] where the data is saved. And it is [383:32] mounted to folder two. So this is where [383:35] the volume is that is mounted or mapped [383:38] into this destination folder 2. That is [383:41] container 2. How did I find out? It's [383:44] folder two. Now let's do the same for [383:47] the other container. So let me docker ps [383:50] again. And I'm going to use the same [383:54] thing, same command. And then the second [383:57] container. [384:00] And if we go up again to the mounts, [384:02] you'll find that it is mapped [384:06] into folder one. So this is container [384:08] one. So this is in the container and [384:10] that is the source on the host and it is [384:13] volume two. So it's very clear that how [384:15] the mounting works and also we have [384:17] proven using different containers that [384:20] they can share the data on the volume [384:22] and they can both mount the volume at [384:24] the same time. Right? Let me now [384:26] demonstrate how we can do the read only [384:29] option. [384:30] So let's go on the home again and let's [384:34] do a docker run and I'm going also to [384:38] use it and this is going to be also [384:41] mounting volume 2 at the let me call it [384:45] folder three because this is container 3 [384:48] and this is going to be read only. [384:51] This is from Ubuntu image and it's going [384:54] to run a bash command. Let's go ahead [384:56] and look at this and let me ls [385:01] cd folder 3 which is right here in to [385:05] get into the container or the volume and [385:07] be able to read and write. If I do ls I [385:11] can look at container one and container [385:13] two. Can I cut their content? Let's find [385:16] out. Container one.ext or container [385:19] 2.ext. Yes, I can look at it. And then [385:22] how about container one.ext? I can look [385:26] at it as well. Now, can I create a [385:28] directory in this volume? And this is a [385:31] right action. So, let me see if I can do [385:33] make directory. And I'm going to call it [385:35] nano test. You'll get an error. Cannot [385:39] create directory. You have only read [385:41] access to the file system. So, that [385:44] proves that I can read. I cannot delete. [385:47] Can I do remove container one text? [385:51] Let's see. I can't because it's read [385:54] only access to the file system. One last [385:57] thing that we would like to see is how [385:59] would the mounting for this container is [386:02] going to look like compared to the [386:04] others. So in order to do that again I'm [386:06] going to open a new connection to the [386:09] host because I want them all to be [386:11] running. I don't want to disconnect any [386:13] one of them. [386:16] And let's do sudo su. And I'm going to [386:19] do docker ps. And I have three [386:21] containers running. And I'm going to [386:22] look at the one the most recent one. And [386:25] this is container 3. So let's do this [386:28] docker inspect [386:31] this container. [386:33] And if you look at the mount, you'll [386:36] find something different here. [386:39] See here read the read is false. So this [386:42] is on folder three, the same volume. The [386:44] source is the same volume, volume two. [386:47] And this is folder three on container [386:49] three. But you'll see here that the read [386:50] write is false. So it has only read [386:52] only. Whereas if I do the same but for [386:56] the other containers. So let's just pick [386:58] one of them because they're going to be [386:59] the same. Let me take this one and I'm [387:01] going to repeat the command. Let me [387:03] remove this and replace it with the ID [387:06] that ends with 7 E6 for the second one. [387:10] And if you hit enter and you look at the [387:12] mount, you'll find that the mount in [387:13] this case, I think I skipped it. It [387:17] should be here. Yeah, here you'll find [387:20] that read write is true. So if you did [387:22] not specify the read only option when [387:25] you are doing the volume mapping between [387:27] the volume and the path in the [387:28] container. If you don't do the column [387:30] read only by default it's read write but [387:33] if you do it then it's read only and [387:34] then you have seen how it behaves. The [387:36] second type or solution to persist data [387:40] in docker is called docker bind mount or [387:43] docker bind mounting. If you hear either [387:46] of them, this is exactly the same thing. [387:50] And sometimes it's also called the host [387:53] path. So what's the story behind this [387:55] solution? [387:57] In the docker volume or the named docker [388:00] volumes, we have discussed that a [388:03] container with a volume, the volume is [388:05] going to be in the docker controlled [388:07] area or the storage controlled area [388:10] managed by docker. [388:12] It's going to be a subdirectory in there [388:15] and the container anything written let's [388:18] say if the volume was mapped to the / [388:20] app directory in the container anything [388:23] written into the container is going to [388:25] be actually written into the directory [388:27] for the volume and anything available in [388:30] the volume will be visible from the [388:32] container at least at the read only if [388:34] this is how the mounting happened or it [388:36] could be readr so the container can [388:38] change can add can delete can can manage [388:42] manage or modify the contents of the [388:44] volume. [388:47] So bind mounting on the other hand is [388:50] simply we are linking or mapping or [388:52] mounting a host path a directory on the [388:55] host file system away from the docker [388:58] area. So somewhere outside so it could [389:01] be anywhere outside the docker area [389:04] we mount that or it could be a file to a [389:06] container path or file. So you mount [389:09] directory to directory or file to a [389:10] file. [389:14] The bind mount or the bind mounting may [389:16] be stored anywhere in the host file [389:18] system. It's not only restricted to the [389:20] docker storage area. And bind mounting [389:23] is used with docker run commands and not [389:26] in a docker file. So we cannot do the [389:28] mounting as of now in a docker file. [389:33] Bind mounts they are different than [389:36] named Docker volumes because they are [389:38] perfect for development and testing. [389:41] In this solution if we would like to [389:44] change the volume it is highly not [389:46] recommended to touch it from the file [389:48] system. So you need to initiate a [389:50] container mount the volume and then [389:52] delete or add or change files in the [389:55] volume and then you can mount the volume [389:58] into other containers and use it. [390:01] Whereas in the bind mount, let's say [390:05] this is the file or the path on the host [390:08] that we are mounting or mapping into the [390:12] container. Now any change you can do on [390:15] the host because this is on the host. [390:16] It's up to me. I can add files. I can [390:18] add HTML files. I can add whatever I [390:21] like. And any changes you do here, it [390:24] will immediately reflect in the [390:25] container. So for development and [390:27] testing this is more handy than [390:29] launching a container and then mounting [390:31] the volume and then changing the content [390:33] of the volume. So for development and [390:35] testing this is perfect for production. [390:37] Go ahead with the named volumes. [390:42] Can I do the docker bind mounts using [390:44] the docker run command? And this is an [390:47] example. docker run hyphen v still like [390:50] we did hyphen v with the name docker [390:53] volumes and then the path on the host [390:57] colon the path on the container. So this [391:01] path and its content and any changes [391:03] that happen to it will immediately [391:06] reflect into this path inside the [391:08] container and any image engine X my [391:11] image Ubuntu or whatever the SL app [391:14] directory in the container will be [391:15] mapped directly to the host path home [391:18] user project [391:21] and we can also do docker run instead of [391:24] giving a fixed [391:26] path in the host I can do dollar sign [391:30] and then parenthesise pwd print the [391:32] working directory. So where wherever I [391:35] am when I run the docker run command [391:38] this directory is going to be mapped to [391:41] / app in the container that I'm going to [391:44] create from my dev image or Ubuntu [391:46] engineext or whatsoever. So anything now [391:49] I will do on the current working [391:50] directory is going to immediately [391:52] reflect in the container that was [391:53] created. So I could be working on that [391:56] same directory with VS code or Vim or [391:59] index html files or anything. And this [392:01] will be reflected immediately to the [392:03] container path under the /app folder. [392:08] Here's an example for this one. [392:11] And here's one more meaningful example. [392:15] Docker run-v and then home user [392:19] engineext.com. [392:20] So this is a file that is usually [392:23] available on the engine x file on the [392:26] host system. So if this was home Ubuntu [392:30] then this is going to be engineext.com [392:33] and then it will map into the container [392:36] under etc engineext engineext.com. [392:42] So this is a file engineext.com created [392:45] and what I'm doing right now is I'm [392:47] mapping this into [392:50] the etc engineext.com [392:52] or the default.com or etc [392:55] xcom.d/default.com. [392:59] So what I'm doing is whatever changes I [393:01] make here they are going to reflect into [393:03] the engine X configuration in the [393:06] container and the container will be from [393:08] engine X image. So this is injecting a [393:12] host specific configuration into the [393:14] container without having to rebuild the [393:17] image again. So this is where it comes [393:19] handy for development and testing. But [393:21] again it's not the best for production. [393:25] So which one to use docker volumes or [393:27] bind mounts? The docker volumes are [393:29] better for production because of the [393:31] following reasons. Number one they are [393:34] in a stored area or a docker storage [393:37] area controlled by Docker. So they are [393:40] safer. They are less errorprone. [393:43] Somebody working in bind mounts on the [393:45] host file system might by mistake delete [393:48] the volumes [393:50] or override their content. They are also [393:53] portable. There is no hardcoded path in [393:55] the file system or anything. [393:58] And they are easier to back up than bind [394:00] mounts. Also the docker volumes are [394:02] better integrated with docker tooling. [394:04] So the different Docker tools, they will [394:06] integrate better with Docker volumes [394:09] than with bind mounts. Let's go ahead [394:11] and play with bind mounts a little bit [394:13] in order to understand how they work and [394:16] how we use them. Right? So let's go [394:17] ahead now and look at how we can persist [394:20] data in Docker using the bind mount or [394:24] the bind mounting or the host path. [394:27] Different names for that. So here is [394:29] what we are going to do. So we have our [394:31] Docker host. We are going to create a [394:33] folder a directory called host hyphen [394:38] folder and this is going to be the full [394:41] path. So this is the default path when [394:44] we get into the docker host and then [394:46] this is the name of the folder [394:48] in your case. Please use pwd print [394:52] working directory to find out where you [394:54] are exactly and then you will add this [394:57] part to it. Okay, so we did that. What [394:59] are we going to do next? We're going to [395:01] create a file with some data into that [395:04] directory and then we are going to use [395:07] this as a volume or a bind mount that is [395:10] going to be used as the persistent [395:13] storage for containers. We are going to [395:16] create and we're going to look at the [395:18] features. Please remember that this is [395:21] binding or a host path mapping into a [395:24] container path. This is not or has [395:27] nothing to do with the docker area. it [395:30] is in the host file system and not in [395:32] the docker area or the docker protected [395:35] and managed storage area in the host. [395:38] All right, let's go ahead to the [395:39] console. So I have multiple terminals [395:42] open and ready for us to start working [395:45] on this. So if I do ls, I don't have [395:48] anything here. So I'm going to create [395:50] make directory and I'm going to call it [395:53] hosty folder. [395:57] I'm going to get into this directory. [396:00] ls I don't have anything and I'm going [396:03] to echo [396:06] and I'm going to say hello this is the [396:10] host [396:13] bind mount [396:17] and this I'm going to direct it into a [396:20] file called hostext [396:25] and if I do ls now I have the file as [396:27] you can see it's right here [396:30] and if I do cat host.ext to see what's [396:34] the content. The content is the message [396:36] that we have written. All right. So that [396:39] sounds good. What do we need to do now? [396:41] Let me go back one step. [396:44] And now I would like to run [396:48] a container in an interactive mode. And [396:50] this is going to be named container one. [396:54] And this will be from an Ubuntu image. [396:57] And I'm going to run the command bash. [396:59] So I need to do the bind mount to the [397:01] container as it gets created. So I'm [397:03] going to do minus v. And then I would [397:05] like to know the path. And what I will [397:08] do is I'm going to take this path [397:10] because that's the path where I am. In [397:13] your case, you can do pwd print working [397:15] directory before you do the docker run. [397:17] So you'll know exactly where you are. [397:20] And this is going to map into a folder [397:24] in the container called container [397:27] folder. If it doesn't exist, it will be [397:29] created. And that is Ubuntu bash. And [397:32] hit enter. And I'm inside the container [397:35] right now. Let's do ls. As you can see [397:38] right here, we have the container [397:40] folder. If I go into the container [397:42] folder and do ls, you'll find that we [397:45] have the host.ext text which was on the [397:49] host path or the host directory and if I [397:52] do cat for the host.ext text it will be [397:56] exactly the same. This is the host bind [397:59] mount. All right. [398:02] Now let me do echo from this side and [398:05] I'm going to echo. Hi, this is container [398:08] one. [398:10] Copy. [398:12] And I'm going to append it. If you do [398:14] two greater than signs, it's going to [398:16] append. If you do only one, it will [398:18] overwrite what is in the file. So I'm [398:20] going to do this for host.ext. [398:25] Now let's do cat host.ext [398:28] and you'll find now that there is the [398:30] original message and the response. If I [398:33] go on the host now and if I do cat host [398:37] folder [398:40] host text you'll find that we have the [398:43] two messages. So now whatever changes on [398:46] the container for this file it's going [398:49] to appear on the host as well. So let's [398:52] go ahead and do CD host folder [398:57] and I'm going to do echo [399:02] I container one [399:04] nice to see you [399:07] and I'm going to append this to host.ext [399:10] again [399:12] if I do cat host.ext [399:15] you'll find that we have all the [399:16] messages and also I'm going to nano [399:24] host to [399:27] do text. [399:29] I'm going to say hi from the host. [399:33] I'm going to do Ctrl X Y save. If I do [399:37] ls, now I have the two files. If I do [399:39] cat host 2.ext, [399:42] you'll find that hi from the host. If I [399:44] go back to the container and in the [399:46] container folder and I do ls, I have two [399:49] files. I have host.ext and host2.ext. If [399:52] I cat host.ext, [399:55] I'll find the message, hi container, [399:58] we're nice to see you. And if I cat host [400:01] 2.ext, you'll find the message, hi from [400:04] the host. So it's very clear why this is [400:07] favorable because I can change anything [400:10] on the host directory and it will [400:13] immediately map or reflect on what the [400:16] container sees. And if this was [400:19] configuration, configuration changes, [400:21] HTML file updates and so on while [400:23] developing and testing. So this is the [400:25] easiest way. I don't have to go into [400:28] creating a new container, mounting the [400:30] named Docker volume, doing the changes [400:33] and then create a new container that [400:35] will use these changes and so on. So [400:38] this is the easiest. You can just update [400:40] on the host and it reflects on the [400:42] container immediately. Now what if I [400:45] have a second container available [400:47] created? [400:48] So let's do also docker run [400:54] and I'm going to run a different [400:57] container but it's going to follow the [401:00] same thing. It's going to mount the same [401:01] volume and again I'm going to get into [401:03] an interactive shell bash and it will [401:07] mount on container folder. If you don't [401:09] want to confuse them, I could I could [401:11] say container 2 folder. So you can [401:15] differentiate between the two and hit [401:18] enter. So now I'm inside the container. [401:20] LS I'll find container 2 folder. And as [401:24] soon as I get into it, [401:29] I can do ls. And as you can see, we have [401:31] host two and we have host.ext and they [401:35] are the same messages. And again I have [401:37] one container that was communicating [401:39] with the host and this one also can [401:41] communicate with the host and say hi [401:43] this is container 2 anybody there [401:49] and we're going to append this to host [401:51] tech or let's let's do it on host 2.ext [401:54] text. [401:57] Let's go in the host [402:01] here and I'm going to go cdhost folder [402:05] ls and cat host 2.ext. You'll find the [402:10] message this container to anybody there. [402:13] So now it's very clear how the different [402:15] containers can use that host folder and [402:18] any update you will do it will reflect [402:20] to all the containers at the same time. [402:22] All right. Now let's inspect the two [402:24] containers and see what we have in terms [402:27] of bind mounts that appear or the mounts [402:30] that appear in the container. So docker [402:31] inspect container one [402:36] if we look at the mount part. So here is [402:39] the mount and the type is bind. Before [402:44] in the name docker volumes it was [402:45] volume. [402:47] The source here is the path home Ubuntu [402:51] host folder [402:53] and destination is container folder. So [402:55] this is container one and it is read [402:57] write. If I do the same to container two [403:05] only difference will be in the folder [403:07] that we are mapping. So the mount type [403:08] is bind source the same but here it's a [403:12] different one and read write as well. If [403:15] you go up in under the binds, you will [403:18] find that also there is some [403:21] host config binds home Ubuntu host [403:25] folder is mapped to container 2 folder [403:28] as you can see. So you can look at it at [403:30] the host config or in the mounts. The [403:32] mounts will give you the source and [403:33] destination. But here also it's very [403:35] clear because the colon separates the [403:36] source from the destination. So let's [403:40] now create a third container and we are [403:42] going to do the bind mount but with read [403:44] only access and we'll see how it [403:45] behaves. So I'm going to do docker run [403:49] minus it and then the name is container [403:52] 3 and I'm going to do the host path or [403:55] the bind mount and this will be to this [403:58] path. So home Ubuntu [404:03] and then the name is host-en folder and [404:07] this will mount at the container 3 [404:11] folder. If the folder does not exist, it [404:13] will be created read only and this is [404:16] going to be Ubuntu and the command that [404:19] will run is bash. Now let me ls and we [404:23] have container 3 folder as you can see [404:25] here. If I do cd cont 3 folder and do [404:30] ls, we have the two files as you can [404:32] see. If I want to echo as I did with the [404:35] other containers and say hi, this is [404:39] container 3 and try to append file [404:44] host.ext for example, you'll get an [404:46] error that this is read only system. But [404:49] if I try to cat host.ext read the [404:52] content, I can read the content. If I [404:55] want to do the same for host2.ext, I [404:58] should be able to do it as well. But if [405:00] I try to create directory or create a [405:04] file or change a file, I will not be [405:06] able to. All right. So hopefully this [405:08] explains exactly how this works. [405:12] If I get here, I don't need container 2 [405:15] anymore. So I'm going to exit. So I'm [405:17] now back on the host. If I do docker [405:19] inspect container 3, let's see how the [405:23] the mount would look like. [405:27] So here readrite is false. Whereas bind [405:31] is the type and then the source and [405:33] destination are clear. And if I look at [405:35] the host config, I should also find some [405:37] highlights about this here. Host config [405:40] binds. And here's the bind. But it shows [405:43] that it is read only. All right. So [405:45] hopefully this is clear to you. [405:53] All right, let's now go over what Docker [405:56] Compose is and what we can use it for in [406:00] order to deploy multiple container [406:03] applications and we don't have to do it [406:06] one by one. So we can define a script [406:10] that is going to have the configuration [406:12] for the desired containers for the end [406:15] state that we would like to have and [406:17] then docker compose will execute that [406:19] file and deploy what we need to do. [406:23] So docker compose can help us to [406:25] simultaneously create start stop or [406:28] delete multiple containers on the same [406:31] docker host. So we are still focusing on [406:34] a single Docker host and that's what we [406:36] are working with. [406:38] So if I have an container that is [406:41] supposed to run a NodeJS application and [406:44] maybe I need a database also for this [406:46] application [406:48] then I can use docker compose in order [406:51] to create the many containers that I [406:54] need for this application. [406:58] So what is docker compose? It's nothing [407:00] but a tool software tool under docker [407:02] that we can use it to define and manage [407:06] multicontainer docker applications. [407:10] So where do we define it the [407:12] multicontainer application we create a [407:15] file by default or the default name for [407:18] that yl file is docker composyiml [407:22] or yl. So you can define all your [407:26] environment including services, [407:28] networking, volumes, containers, [407:30] dependencies, all of that could be [407:33] defined in a YML file and then you can [407:36] execute the AML file using docker [407:38] compose using a single command and this [407:41] will deploy whatever you have specified [407:44] inside the file. [407:49] And if some of these containers you have [407:52] docker files for defining how the images [407:56] for these containers should be then you [407:58] can also use docker compose to build the [408:01] images [408:03] or to build the images and then create [408:06] the container. So these both are [408:08] possible and you can define or specify [408:10] where to locate these docker files and [408:12] docker compose is going to take care of [408:14] the rest. [408:17] So let's look at how the workflow would [408:20] be. So you need to define the YAML file [408:22] which is by default the dockery compos. [408:26] That's the default name but you can use [408:27] alternate names if you would like. [408:30] This YAML file will reference docker [408:33] files. If you have docker files that [408:36] need to be used to create images for one [408:40] or more containers that are defined in [408:42] the aml file. [408:44] So when we have that then docker compose [408:47] when you execute the ML file is going to [408:50] grab the docker files and then build the [408:52] required images [408:54] but it can also pull readymade images [408:57] from your local host or maybe from [409:00] docker hub and then it's going to create [409:02] the containers that you need and as we [409:05] build it with a single command we can [409:07] also tear it down with a single command [409:09] we can stop it we can restart it and we [409:12] can delete it completely. Let's now look [409:14] at the docker compose file structure. [409:18] How does it look like? What's the [409:19] syntax? How do we define the containers? [409:22] What are the names if any? What are the [409:24] parameters we need to define? That's [409:26] what we are going to look at right now. [409:29] So the first thing we need to know about [409:32] docker compose is the section called [409:34] services. The services is written and [409:38] these are the containers that you would [409:40] like to create using this docker compose [409:43] yl file and it is written lowerase [409:46] services and then a column. [409:49] So in this example we are going to [409:51] create three services or at the end [409:53] we're going to get three containers. One [409:55] has the local name in the compos file [409:59] database front end and then back end. So [410:02] these are the three that we are going to [410:04] create and please notice the [410:06] indentation. So each one of them starts [410:09] two spaces from the left and then you [410:12] started and these are all indented. So [410:14] they are all at the same space or same [410:18] distance from the left hand side. So I [410:20] have database column, front end column, [410:22] back end column. These names are locally [410:25] significant only in the docker compose [410:27] file. So these are not going to affect [410:29] anything else. You can name it John [410:31] Smith and Sarah if you would like to. [410:33] That's up to you. [410:37] The second thing we need to look at is [410:39] the service image or the image. So if [410:42] you have any of your containers is going [410:45] to be created from a readym made image [410:49] with whether it is on your local host or [410:51] on docker hub. Then you can use the part [410:56] image [410:58] and again notice the indentation from [411:01] here to here. So you have to move couple [411:03] of spaces in because this is an item or [411:06] a parameter that is under this service [411:09] and the service name is database. So [411:12] image lower case colon and then the name [411:14] of the image or you can have the version [411:17] if you'd like to the tag as we call it. [411:21] Then if you would like for one of the [411:24] services that docker compose is going to [411:27] build the image for that specific [411:29] service then we need to add the build [411:32] statement in the docker compose file. [411:35] Assuming that in this case we have a [411:38] docker file in the same directory as the [411:41] docker compos yl file then all what we [411:44] need to do is to add a build statement. [411:46] So in this case I'm assuming that front [411:48] end needs an image created from a docker [411:52] file and the docker file exists on the [411:54] same directory in the same directory [411:56] where the docker compos file is. That's [411:59] why we type build lowerase colon and [412:01] then dot means the current directory. [412:06] What if I have the docker file in a [412:08] different directory? It's not in the [412:10] same directory as the file. How can I [412:13] specify the path to that file? And if it [412:17] is not named docker file, it has an [412:18] alternate name. What do I do? How do I [412:21] specify the path? And how do I specify [412:24] the alternate name for the docker file? [412:26] And where do I define that specifically? [412:30] So if we assume that the back end has a [412:33] docker file with a different name in a [412:35] different directory, we need to define [412:37] that here. So again it is going to be a [412:40] build section. Again the indentation to [412:43] the right build column and then we are [412:46] not going to write anything here. We'll [412:49] leave this this one blank and underneath [412:52] again indentation two spaces to the [412:54] right we write context and colon and [412:58] then the full path to where the [413:01] alternate docker file exists. So this in [413:04] this case user project app. This is what [413:06] we are assuming where the docker file [413:10] exists and the name of the docker file [413:12] can be specified using docker file colon [413:16] and then the file name. Here the [413:17] assumption is the alternate docker file [413:20] name is file config. And please note [413:23] that these two are on the same [413:25] indentation from build. So this one and [413:28] this one both are under the same build [413:31] section. So that means these are [413:33] parameters for the build. [413:36] Next, what if I need to define a [413:39] container name. So in this case under [413:43] the service and aligned or equal [413:47] indentation from the left hand side, [413:50] right container name and colon [413:52] everything lower case and then the name [413:54] you desire to have for the container. I [413:57] can have this under each container if I [413:59] want to. [414:02] Then what if you need to expose ports [414:04] for a certain container? Then again [414:08] under the parameters image container [414:11] ports or build ports you can define [414:14] ports colon and then enter indent two [414:20] spaces and then hyphen comma host port [414:25] colon container port and then close the [414:28] quote. In some formats you can do it [414:30] without the the quotes but it's better [414:33] to follow one way that works for you and [414:36] then you continue doing it. So this is [414:39] how we expose ports. This is equivalent [414:41] to when we do the hyphen p lowerase or [414:44] the hyphen publish in order to expose [414:47] the port with docker run. [414:50] Then what if we need to add a bind mount [414:53] to one of the services or to multiple [414:55] services? What do we do? So again on the [414:58] same indentation, same line, we write [415:00] volumes and then colon and then we hit [415:03] enter and two spaces to the right hyphen [415:06] and then put the directory or the host [415:10] path the folder the full path for the [415:12] folder on the docker host colon where [415:17] it's going to map inside the container. [415:19] So the container path and the host path [415:22] and that's it. That's all what you need [415:23] to do for the bind mount. What if it is [415:26] a normal volume, a named volume, what do [415:29] we need to do? So in this case, you need [415:31] to do two different things under the [415:33] corresponding service. Let's say I want [415:35] to do it under database. So what you [415:38] need to do here is you will define the [415:40] volumes again. In this case, you need to [415:43] also indent. So this will be indented [415:46] underneath and then the volume name [415:50] colon container path. So this is an a [415:53] named volume that you have to create [415:55] beforehand but we haven't done it [415:57] anywhere else and that's why we have to [415:59] create that in a volume section. So we [416:02] have the services section and at the [416:04] same indentation we have volumes. So [416:08] services is containers volumes is named [416:11] volumes and then you can write the [416:13] volume name. So as you can see here the [416:16] same name is used here. [416:21] Then what if I need to create a volume [416:24] but it's not going to be named an [416:25] anonymous volume. I don't want to create [416:28] the container beforehand as we did in [416:30] the previous slide. So what do I do in [416:32] that case? You do the volumes, you do [416:34] the indentation and you don't put the [416:36] volume name. You just leave it blank and [416:38] then do colon container path. So this is [416:41] going to create a a volume anonymous [416:44] volume or a volume with an anonymous [416:46] name and it's going to be mapped to the [416:48] container path inside the container. All [416:51] right. So these are the critical ones [416:53] that we need to create if we need to [416:55] deal with Docker compos file. So now we [416:57] learned how to do containers or services [417:00] and how we define the container name, [417:02] how you define the image if it is ready [417:04] on the host or from docker hub. how to [417:06] do the build if you have a docker file [417:08] in the same directory as the docker [417:11] compose file or if it is in a different [417:15] directory and if it has a different and [417:18] if it has a different name and we do [417:20] that under the build. We learned also [417:23] how we can expose ports and we learned [417:25] how we can create volumes whether they [417:28] are bind mounts or named volumes or they [417:32] are anonymous volumes. So that's enough [417:35] for us to practice a little bit and play [417:37] with it in the lab. I'll see you in the [417:39] next video. Let's now look at the docker [417:42] compose command. So we have built the [417:44] YAML file for docker compose and now we [417:47] need to start creating stopping [417:50] restarting the environment. What do we [417:51] do? So there are multiple commands and [417:54] they are all start with docker space [417:57] compose. It used to be in the older [417:58] version docker compose but this is the [418:01] case right now. Docker compose build. If [418:04] I have created the docker compos file [418:07] and it has build sections under the [418:10] services. So images needs to be built. [418:13] Then in this case I can do docker [418:14] compose build and it's going to build [418:17] the images that are in the docker [418:20] compose yl file that exists in the [418:23] directory where you are running this [418:25] command. [418:26] If I have multiple services but I need [418:28] to run one of them. So for example in [418:30] the uh previous file we looked at [418:32] database front end back end let's say I [418:34] only need to start front end for some [418:37] reason for some testing what do I do you [418:39] can do docker compose run and service [418:43] name which one database front end back [418:45] end notice in these two commands I did [418:48] not specify anything about the name of [418:51] the docker compose file so this assumes [418:53] that it is on the same directory where [418:56] you are applying these commands you have [418:59] the docker compos yl file in the same [419:01] directory. [419:03] Then if I want to run the entire service [419:06] or environment that is defined in the [419:08] docker compos yl file I do docker [419:11] compose up. So this will build the [419:13] images if they are not located locally [419:16] and starts the container. So even if you [419:19] haven't done the docker compose build [419:21] this is going to do the build and run as [419:24] well for all the services. So this [419:26] command is for a specific service. This [419:28] is for all the services. What if I need [419:31] to run it in detached mode? I can run [419:33] also up with hyphen d which means start [419:36] the containers in detached mode. What if [419:40] the file name is different? Then I can [419:42] do docker compose hyphen f and then I [419:46] can specify the file name and up. And of [419:48] course you can specify the path for the [419:50] file name and up. And that means a [419:52] different docker compose file builds the [419:55] images and starts the containers. [419:59] And this is the minusd that I told you [420:02] about. And then we have few other [420:05] commands. Docker compose down. So it was [420:07] up. Now I would like to stop the [420:10] containers and delete all the containers [420:13] created by docker compose up. [420:16] And of course you can do down docker [420:19] compos down hyphen volumes which means [420:22] delete and remove the containers but [420:24] also delete the volumes that they have [420:27] been created. And in this case we are [420:28] talking about the named volumes and the [420:30] anonymous volumes that were created by [420:32] docker compose [420:35] docker compose down with hyphen remove [420:38] orphans. Let's say that this docker [420:41] compos file created containers but then [420:43] you changed the file and some of the [420:44] containers were removed but they are [420:46] still on the system. They are exited or [420:49] stopped on the system and I would like [420:51] to remove the current ones and also the [420:54] ones that have been before used and [420:57] created they are now stopped and I'm not [420:59] using them. So you can do hyphen hyphen [421:01] remove orphans and of course you can [421:03] combine volumes hyphen hyphen volume [421:06] space hyphen hyphen remove orphans as [421:08] well and you can do docker compose [421:10] volumes and remove or orphans which is [421:13] the combination of the previous two and [421:14] also we can do docker compose stop which [421:17] will stop the environment stop the [421:19] containers and docker compose start [421:21] which will restart the containers again. [421:26] When you use docker compose to build an [421:29] environment, docker compose will [421:30] voluntarily is going to create a bridge [421:34] network and all the containers in that [421:36] environment that are created by docker [421:39] compose are going to attach or are going [421:41] to connect on that bridge network. [421:46] So when you do this up minus D then and [421:49] you do my docker network list you will [421:52] find that there is one called Ubuntu [421:54] default and it's of type bridge. Enough [421:57] for the theory and commands and let's go [421:59] ahead and start playing with docker [422:01] compose. I'll see you in the next video. [422:03] First docker compose files and see how [422:06] they work. So let's go ahead and create [422:09] our first docker compose file. I can do [422:12] it in the nano editor in the docker host [422:15] but VS code as an IDE will give you [422:19] better support as you build because you [422:21] have the Docker plug-in in VS code. So [422:24] what do we need to do? I'm going to [422:26] create first thing services and then I'm [422:29] going to hit enter and then space space [422:31] for indentation and I'm going to call [422:34] the first service web also enter space [422:38] two spaces and then here I'm going to [422:41] write container name I want to create a [422:45] container with the name dolphin at after [422:47] the column we leave space [422:50] and then I want to expose ports [422:55] space space [422:57] then I'm going to expose port 8080 on [423:01] the host to port 80 on the container or [423:05] the service. [423:07] Then [423:09] I need to define that the image is going [423:11] to be engine X. [423:15] So that's it for the first configuration [423:18] file. I'm going to take this copy. I'm [423:20] going to nano. [423:22] The file name will be dockery- compose. [423:25] That's the default name. Yiml yaml. I'm [423:29] going to paste what we have typed. And [423:32] then I'm going to do Ctrl X. Yes. And [423:35] enter. Now if I cut that file, [423:41] you'll find this is what we wanted. We [423:43] need services. It's called web container [423:45] name dolphin ad ports and image. Of [423:48] course, you you may want to put the [423:49] image on top, the container name at the [423:51] end, but this is how it is. Now, before [423:55] we do anything, let's see what networks [423:58] we have on the host. And you'll find [424:00] that we have the three default ones. We [424:03] don't have any other networks at the [424:04] moment. All right. So, let's bring [424:06] docker compose up. So, we do docker [424:09] compose. Note that in the file name [424:12] there's a hyphen. Here there is no [424:14] hyphen. And I'm going to write up and [424:17] minus D in detached mode. [424:21] So what's happening now? Running one of [424:24] two [424:25] creating network Ubuntu default then [424:29] network Ubuntu default and then running [424:32] two of two where container dolphin ad [424:35] has been created and now is started. So [424:38] let's do docker ps. [424:41] As you can see we have a container up. [424:43] The name is dolphin eb. The mapping is [424:46] done port 8080 to port 80 on the [424:48] container. So this is on the host side. [424:50] This is on the container side. Has been [424:52] up for 20 seconds and it is an engine x [424:55] image and it's running in detached mode [424:58] because we instructed that. Now let's [425:00] clear [425:02] let's do docker network ls. Find out if [425:05] we have any networks any new networks. [425:07] And if you look at the last one, you [425:10] have Ubuntu_Default [425:12] bridge. It didn't exist before we used [425:15] docker compose which means that this was [425:18] done by docker compos and also we have [425:20] seen it when it was running when we did [425:22] the docker compose up. [425:25] All right. What if I inspect the [425:27] networking in dolphin at the container. [425:30] So let's look at what we have here. So [425:32] first thing it has been on a custom [425:36] network a custom bridge as you can see [425:40] the IP address is 17218 the default [425:43] bridge is 1727 [425:47] and for the network binding for the [425:49] container it is on Ubuntu default as you [425:52] can see [425:55] and you have an alias of web for the [425:57] service and dolphin ed for the [425:59] container. [426:03] And here we have the ports [426:06] ATTCP on the container to the host IP [426:10] whatever that is and then port 8080 on [426:13] the host. So everything we have created [426:16] is available in the settings that went [426:19] into the container and the docker compos [426:22] version. [426:24] And who is the maintainer of the image? [426:27] The rest is not networking. The the rest [426:29] is just the normal stuff we have seen [426:31] before. Now let's see if I can get to [426:33] the container from the outside because [426:35] we have seen the mapping of the port. [426:37] Let's find out if we can do it. So I'm [426:38] going to take the public IPv4 address of [426:42] the docker host and I'm going to go out [426:44] and I'm going to open a browser to port [426:47] 8080 as we have typed it. And as you can [426:50] see, engine X. So container is created, [426:54] publishing port is done, everything is [426:56] done. And now I can get to the default [426:58] page of the container. So that's the [427:01] simplest form creating one container [427:03] using docker compose. But that's not the [427:06] strength of docker compose. What if we [427:08] do docker compose stop? [427:23] Now it has stopped the container as you [427:26] can see. And if I do docker ps I don't [427:29] have any running containers. If I do [427:31] docker ps minus a then I can see that [427:34] there is one container that was stopped. [427:37] And I can also, by the way, do docker [427:39] compose psfs because if I have [427:41] containers created without docker [427:43] compose and others with docker compose, [427:46] this is going to tell me if I have any [427:49] created and running using docker [427:50] compose. And if I do this minus a, it [427:53] will tell me the ones created by docker [427:55] compose and are in a stopped state. All [427:58] right, [428:00] let's say I want to start it again. So [428:03] I'm going to do docker compose start. [428:05] And as you can see it is starting. And [428:06] if I repeat the command, [428:10] you'll see that there is one that is up [428:12] and the service is web and the name is [428:15] dolphin add here. And this is the [428:19] command, the entry point uh command that [428:21] was done and the port mapping that we [428:24] have instructed as well. And it shows [428:26] you here the time it has taken to bring [428:28] this up. Now let's say I'm done. I don't [428:32] need it anymore. So what do I do? You [428:33] can do docker compose. So we do stop [428:37] start and now if you do down [428:40] then it is removing the container and [428:44] removing the network as well. So if you [428:46] do docker network ls again you'll find [428:49] that we don't have the Ubuntu default [428:53] anymore. And if I do docker compose ps [428:57] minus a [428:59] minus a. And you see that we don't have [429:02] containers exited or up and running as [429:06] well. [429:12] So let's now do this docker project. And [429:15] what we are going to do, we're going to [429:16] assume that you are now an [429:18] infrastructure and someone who is an [429:21] expert in Docker [429:23] and someone hired you because they need [429:26] to establish a website using Docker on [429:29] AWS and they have specified the specific [429:34] template they would like to use and they [429:36] are going to provide you that template [429:38] or maybe you are on the template website [429:42] and you can buy it for them and you just [429:43] bundle that in your cost. So they like [429:46] the template and now you are going to do [429:47] the project end to end. You are going to [429:49] build for them the front end which is [429:52] the website. So we are not going to [429:53] touch on the database in this project [429:56] but you are going to build them the [429:57] website [429:59] using the template using docker and you [430:01] are going to build it from the docker [430:03] file to the image to establishing that [430:06] website and making sure that it is live [430:08] online. So let's find out what we are [430:11] going to do. So let's assume that they [430:13] have been shopping around and they liked [430:16] on Invato Elements. They liked this [430:19] template and they would like to use this [430:22] as their website. So this is what you [430:25] are going to build for them. Database is [430:27] going to come next but for now they want [430:30] to see that this website is live and how [430:32] it would look like and that it can be [430:34] done with containers on AWS. [430:38] So they like that and they provided you [430:40] a link where the school website or the [430:43] template is on GitHub or maybe you [430:46] bought the template and you uploaded [430:47] everything on GitHub. This is out of [430:49] scope for now uploading the templates [430:51] and buying the templates and all that [430:53] but the templates is available right now [430:55] and it is on GitHub and you have the [430:58] link to clone it and now it's time to [431:00] start working. [431:04] So we start from GitHub. We're going to [431:06] clone that. We're going to copy that, [431:08] download it into the Docker host. And [431:11] then from the Docker host, we are going [431:12] to build the Docker file that will use [431:16] the code that you have downloaded and [431:18] build the image. And once we have built [431:22] the image, everything else, if you have [431:24] done it right, everything else becomes [431:26] easy. We can use that to run with Docker [431:29] run and build the container and then [431:31] test access to the container from your [431:34] laptop or their laptop. just to see how [431:36] it looks and then we can think about the [431:39] next phases [431:40] and then we are going to push this new [431:43] image that we have used when we put all [431:45] the code inside the image we're going to [431:47] push it to docker hub so it can be [431:49] reusable or we can edit some stuff and [431:52] then do version two version three [431:54] version four and so on so it is now [431:56] available for collaboration available if [431:58] you are the consultant and you are going [432:00] to get your pay after you finish and [432:02] then you will leave it so now at least [432:04] you have already uploaded it to them and [432:06] now they can hire you whenever they need [432:07] to make changes or maybe their [432:09] developers can take it from that point [432:11] onwards. Either way, this is what we are [432:14] trying to do now and we are going to [432:16] build a website that will look like that [432:18] what the template shows on the Invato [432:21] elements website. [432:23] So this is how it will look like on the [432:26] docker host and on the container. So [432:28] this is how we need to build it. So on [432:29] the docker host when we clone it on the [432:32] Ubuntu machine on the docker host we are [432:34] going to have a folder once we clone or [432:38] download what's on GitHub it's called [432:40] docker capstone project one and if we [432:42] list the content of this directory we're [432:45] going to find school website and if we [432:46] ls the contents of school website we'll [432:49] find index and error and about there's a [432:52] lot of things and then we're going to [432:54] also find directories called assets [432:56] documentation source and so on. So this [432:59] is how it looks like on GitHub and on [433:02] your laptop when you download it. And [433:03] we're going to verify this. The way we [433:06] want this to be is since this is the [433:09] content and the index html file and so [433:12] on, the index html file in engineext the [433:15] default one is under user share engine [433:18] xhtml. So what we need to do is we need [433:21] to get this content with these [433:23] directories and we need to get it copied [433:26] under this folder. So there will be a [433:28] copy here and that's how when we browse [433:31] to the container the website is going to [433:33] be launched or it will appear as per the [433:36] template. So this is exactly what we [433:38] need to do. Of course the key docker [433:41] skills that we are going to demonstrate [433:42] doing this project is how you can write [433:44] and build docker file for a static [433:47] website server or the front end which is [433:50] the template we talked about. [433:52] Understanding the container life cycle [433:54] from build, running to stopping and [433:55] removing. Managing ports and volumes and [433:58] static content in containers and basic [434:01] use of docker compos for service [434:02] orchestration and of course [434:04] containerizing [434:06] a code that you have been given for an [434:08] application or a website into a [434:10] container using docker files and then [434:12] creating docker images. So let's go [434:14] ahead to the console and start working [434:17] on this. All right. So here I am in the [434:20] console right now. What we need to do is [434:22] we need from GitHub where the project is [434:28] either if it is your account you can go [434:30] ahead and copy the code or the access [434:33] how to get to it and it's a public repo [434:35] so you can get the files without any SSH [434:39] or anything and it all depends on how [434:40] you would like to get it. In my case, [434:43] I'm going to download it to my Docker [434:45] host using the command get clone and [434:47] then the URL I just copied. And now this [434:50] is going to be under my Docker host. So, [434:54] as you can see, it has created a Docker [434:56] Capstone project one. And if you'd like [434:59] to see what is in there, [435:03] I do ls. [435:05] Okay. And then we have the readme file [435:07] and the school website. And if we check [435:10] here, it's the readme file and the [435:12] school website. [435:15] If I go into the school website [435:17] directory. [435:23] Okay. So I have to go back into here. [435:29] And if I want to go now into the school [435:32] website directory and we do ls, you'll [435:34] find that there is so many files [435:36] including index html. [435:39] So this is the main page that we have [435:41] seen in the template. [435:44] So this is what we should see and this [435:46] is what the index html is going to [435:49] display. But then it's going to show all [435:50] the menus and so on. So I need to make [435:53] sure that at the end we're going to end [435:55] up with something like this that has [435:56] these pages included. All right, that's [435:59] that's cool. So we have all these files [436:01] here right now. What do you want to do? [436:03] So I'm going to do one step back into [436:06] the project directory. And now it's time [436:08] to create the Docker file. So let's do a [436:11] nano docker file. [436:15] And I'm going to have this created from [436:18] engine X. It's up to you to choose the [436:20] version. For me it's latest. I can add [436:22] column latest or just leave it blank. [436:25] Then we need to copy the code of the [436:27] application of the website of the front [436:29] end into the right directory into engine [436:32] X. What is the right directory into [436:34] engine X? We know as a destination it's [436:36] going to be / user/share slash [436:40] engineext/html. [436:42] But what is the source? The copy is keen [436:46] on the relative path from the directory [436:50] that is considered the build context. [436:52] What is the directory that is considered [436:54] the build do context is the directory [436:56] where I created the docker file and that [436:59] is the docker capstone project one. So [437:03] from there you need to point to where [437:06] the content is. Let me just open this so [437:09] I make it easier for you. Let's open a [437:11] new terminal. [437:13] So it will be easier to understand what [437:15] I'm talking about. Stud. [437:18] And now if you do ls this is where the [437:21] docker capstone project and this is [437:24] where I am creating the docker file. So [437:26] that's why I'm going to move inside it. [437:30] If I do ls now we have the school [437:33] website is where all the content is. So [437:36] I need to tell copy relative because I'm [437:38] going to create the docker file right [437:39] here inside this directory. [437:42] So relative to where you are where the [437:46] docker file is and where the build [437:47] context is. Go into the directory called [437:50] school website and copy all its content [437:54] from where you are from where the docker [437:56] file is. Please copy [438:01] the school website. See, I just made a [438:04] mistake. It has to be exactly the same. [438:06] And of course, I could have came here [438:08] and just copied this to make sure that [438:11] we don't do mistakes, especially if the [438:13] names are long. Can just go here. [438:18] Delete all of this and paste it just to [438:22] make sure we're not doing doing any [438:23] mistakes. Now, this is the source. [438:25] What's the destination? As we mentioned, [438:28] user [438:30] share engine X and HTML. What if you [438:34] working with Apache? Then you need to [438:36] find out the root document of the [438:38] Apache. What if you were working with [438:40] any other tool or any other server? [438:44] Then you need to find out where should [438:46] the main or the root document of that [438:48] server be. And this is where you want to [438:50] copy the files. And then we need to [438:53] expose port 80. That's all what we need [438:55] to do. So Ctrl X, yes, and enter. Now we [438:58] have the Docker file. Let's cut to make [439:00] sure that we have it right [439:03] and we didn't do any mistakes. Now when [439:05] you Oh, see docker [439:09] file. So now from engine X latest and we [439:14] are now as you can see we are at the [439:16] capstone project and this is where when [439:19] we did ls [439:21] capstone project and then we have one [439:23] folder or one directory [439:26] or subd directory and that is the school [439:29] website and this is where all the [439:31] content is when we did ls here [439:33] everything was inside it. All right so [439:36] it looks okay to me. Let's do a docker [439:38] build minus t. I'm going to call it web [439:42] school [439:44] and the build context is the current [439:46] directory. Hit enter and it looks like [439:49] it has created the image without errors. [439:51] Now let's do docker images. [439:56] And we have a web school image right [439:58] here. And now it's time to do a docker [440:01] run and test that to see if it works or [440:03] not. So I'm going to do it detached. And [440:07] then I'm going to do minus P. Let's bind [440:10] the host port 80 to the container port [440:13] 80. I can do a different number if I [440:15] want. I can do host port 3,000, 4,000, [440:17] 5,000, up to me. But since I know that [440:20] this is not used right now, I can use [440:22] 80. Nothing stops me from that. What [440:24] else do you need? I'm going to provide [440:25] it a name. I will call it web school. [440:29] What is the image? And the image is [440:32] going to be web school. And if this is [440:34] only for testing, what you can do is you [440:36] can also add the option rm. So when you [440:40] are exited, the container is going to be [440:42] deleted. And let's hit enter and see [440:45] what's going on. So now I should have a [440:48] container that would look like the [440:49] template available through port 80 on [440:52] this public IP address. So I'm going to [440:54] copy it. If you don't have this or if [440:56] you close this at the beginning to have [440:58] more space to work, you can come here [441:00] and you can copy it from here as well. [441:02] So now let me open a browser to port 80. [441:06] For port 80 you don't have to type it [441:08] but it's up to you. And as you can see [441:11] now we are from port 80 we are having [441:14] something similar to what we have seen [441:16] here. Right? So this is how it looks [441:18] like shell in the background as a [441:20] watermark and then home about classes [441:22] and so on. And in the container we are [441:24] having the same and it looks like the [441:26] same. Yeah some images are missing [441:28] because they need to be added. We don't [441:30] have these images [441:32] but otherwise the templates and the [441:35] details they look like they are [441:37] available here now. All right. So we [441:39] have built that from the template. We [441:42] have containerized the template and now [441:44] it's running inside inside a docker [441:46] container. So it looks like we have been [441:48] successful so far. Okay. So what what [441:51] else do we need to do now? Since I know [441:53] that this one is working, leave it [441:54] working for now. What we'll do is I need [441:57] to push it to [441:59] docker hub and I am logged in into my [442:02] docker hub and if I go in [442:07] this is my account and if I look at [442:09] repos [442:12] I have no repos available and I can [442:14] create one and let me try and call it [442:17] school [442:18] website version one or I can push the [442:21] tag as version one if I want. So I can [442:23] just call it school website because [442:25] you're going to have multiple versions. [442:27] This is the template for the school [442:31] website [442:32] front end [442:36] create it. [442:38] Okay. So it's empty right now but I can [442:42] take this command here as you can see [442:45] and I can use it in order to tag and [442:48] then push. [442:51] So I can do from here docker [442:54] tag [442:56] and then the image name. Of course I [442:59] could have done it just paste this [443:01] command [443:03] and instead of [443:06] push I will do tag now and then I will [443:09] delete these two and then I I need to [443:11] decide on what is the tag that I'm going [443:13] to use. Is it going to be latest or [443:15] because this is the first one I'm going [443:17] to call it version one. [443:22] Okay. So now I'm tagging that um sorry. [443:25] Okay. So I need to put the original name [443:27] first [443:29] which was in the docker run. [443:36] So let's put the name of the image web [443:38] school [443:41] and I'm going to get here. So this is [443:43] the original image and this is where I [443:45] want it to be tagged as. Hit enter. Now [443:48] if I do docker images, [443:50] we'll find that one here that is ready [443:52] to be pushed and it's version one. So [443:54] next step is I I will docker [443:58] login if you are not logged in but I am [444:00] logged in. Then I'm going to do docker [444:03] push the name from here and it is [444:06] version one. So it's exactly this one [444:09] and version one. Let's push and see what [444:12] happens now. [444:14] So it's pushing the image. If it [444:17] finishes properly, then we are done with [444:20] this hands-on lab. [444:22] So, it looks like it did it. And if I go [444:24] to Docker home again, Docker Hub, and [444:28] refresh this page, [444:33] you'll find that we have version one. [444:35] Click on see all. Then this is the image [444:38] that you can pull and use it. So, let's [444:40] do one thing. And this is optional. It's [444:41] up to you if you would like to do it. [444:43] What I will do now is I'm going to do cd [444:48] and I'm going to delete the files from [444:51] here completely and I'm going to stop [444:53] the container as well. So docker ps [444:55] minus a. I'm going to do docker rm minus [444:58] f and then I'm going to stop this [445:00] container which is running the website [445:02] right now. [445:04] So if I go here and I reload, I [445:07] shouldn't get it. Yeah, because I [445:09] stopped it. Okay, so that's a good step. [445:12] If I do docker images, [445:14] I'm going to find the web school image [445:16] here. So I want to delete it as well. So [445:18] I'm going to do docker rmi. And if I do [445:21] docker images again, I don't have it. [445:25] And also I'm going to docker rmi the one [445:29] that we pushed the tagged or the alias. [445:33] So version one. And if we do docker [445:35] images one more time, [445:39] we don't have it at all. So I don't have [445:41] the image web school. I don't have also [445:43] the one I pushed to docker hub. So what [445:45] do we have? What's what do we still [445:47] have? LS we have the docker capstone [445:49] project. Let me also remove that one. [445:50] I'm going to do rmrf. So remove it even [445:54] if it's non empty. And I'm going to [445:57] paste that. Now let's see ls. I don't [446:00] have anything. So what I will do now is [446:02] I'm going to use the docker pull that we [446:04] have seen to test that the image that we [446:07] have uploaded is working. I'm going to [446:10] go back and I'm going to do a docker [446:12] pull [446:15] already exists because there are layers [446:17] cached. That's fine. Docker images. I [446:20] should find version one available again. [446:22] And if I do docker run [446:25] minusd from this image [446:31] v1 and expose port 8080 [446:39] because I'm not using this [446:41] container is running and if we try the [446:44] same IP again I should be able to see it [446:47] again. All right. So what we have done [446:48] quickly we have built the docker file [446:51] after we downloaded the content from [446:53] GitHub [446:55] in the docker file we have copied the [446:58] content of the project the code of the [447:00] project the code of the application the [447:02] code of the front end it's exactly the [447:04] same process no matter what you are [447:05] trying to run in the container and then [447:08] we put that into the right folder under [447:10] engine x which is the user share engine [447:12] x html why that folder because this is [447:15] what engine x browses or displays when [447:19] someone goes HTTP into the EngineX [447:21] server. From there, we were okay to [447:25] build the Docker image from the Docker [447:27] file. And then we built a container from [447:30] the Docker image and we exposed port 80 [447:32] on another port on the host. 80 on the [447:35] container mapped statically to a port on [447:38] the host. We browsed to it. Everything [447:40] worked fine. So we went back and then we [447:43] tagged the image with the Docker [447:48] repository path, the account name and [447:51] the repository on Docker Hub and we [447:55] tagged it as version one because this is [447:56] the first one. Maybe we'll do [447:57] modifications and then we pushed it into [447:59] Docker Hub and then we pulled it again [448:02] and we used it and it was working fine. [448:04] So project is 100% success. It shows you [448:07] the life cycle of an application from [448:09] the code into a docker file and how it [448:12] gets put the right way into the server [448:15] that you are using and then it was [448:18] available for access. So what is missing [448:20] now the back end and the database to [448:23] provide all the images and course [448:25] details and everything that we need. [448:27] Congratulations on finishing up the [448:29] course. If you would like to learn more [448:31] about Docker and at the same time [448:33] support us develop more free and quality [448:35] content like this, consider buying the [448:38] VIP package that includes a lot of [448:40] things. So by doing that, you are going [448:42] to have lifetime access to the course [448:44] and any updates that happen to this [448:46] course. You are going also to have [448:48] access to another 8 hours of video [448:52] content that will have more hands-on [448:54] labs, more topics covered at a deeper [448:57] level. And you will have a second [449:00] realworld project that will help you [449:03] sharpen and harness your real world [449:05] experience and your portfolio as well. [449:08] You will have an access to a community [449:09] for faster Q&A support throughout the [449:12] learning. And you will have of course [449:14] quizzes and assignments in each one of [449:16] the modules. And most importantly, you [449:18] will have access to the 330 PDF guide [449:21] and all the hands-on lab scripts that we [449:24] have used in the course. So if you are [449:27] willing to support us and also have a [449:29] great return on investment through [449:32] further free content video that we are [449:34] going to generate this is going to be [449:36] the link [449:37] www.dolphinaded.com/courses/doccker. [449:41] I hope that you are enjoying or have [449:43] enjoyed the course and looking forward [449:45] to see you in further