 Hello and welcome. My name is Vinícius, and today I'll show you the new updates, the containers extension of Windows Admin Center. Getting started with containers can be a difficult task if you are a Windows admin that has to use PowerShell or the Visual Studio Code. Commands like, for example, Docker PS if you want to check the containers that you have running. Docker Images for checking what are the images that you have in your container host. Are simple commands that every Windows admin will be using when dealing with Windows containers. For every container operation, there's a corresponding Docker command. Docker Run, Docker Build, Docker Pull, Docker Push. These are all commands that you'll be using on a day-to-day basis to manage your Windows containers. However, there is a better way now. You can use Windows Admin Center with the new containers extension. For some day-to-day operations. To get started, let's head into the settings. Go to Extensions. The first thing you want to do is you want to add a new feed for WAC Insiders feed. This feed allows me to add the new containers extension that has been updated for insiders. It's important to notice that you don't have to run the insiders version of Windows Admin Center itself. You just have to add this new feed. Once you do that, the containers extension will show up as an available extension. You can install that and once installed, you can go to the installed extensions, and you can check that the containers extension has been installed correctly. Now let's head back to managing my server. This server that I'm going to manage is a container host, so the containers extension shows up nicely. I can click the containers extension, and the previous functionality that was in this extension is a stdr. I can see the summary, I can see the containers that I have running, I can see networks, volumes, but more importantly, I can see the images that I have hosted in this container host. I can select one of the images, I can see the details of those images, and so on. Now, if I need a new image, I can probably check the Docker Hub. The Docker Hub is where Microsoft hosts all of our images like the Windows Server Core, for example. NanoServer, IIS, .NET, these are all images that Microsoft has pre-configured for you to use. You can get the information like, for example, what is the image name, and what is the tag you want to use. For example, for the Server Core image, we have multiple tags, including the 2004 that has been launched recently. If we go back to Windows Admin Center, and you want to pull an image for Docker Hub, all you have to do is click pull, and provide the image and the tag that you want to pull and click the pull button. If the register that you want to pull an image from requires you to authenticate, you can click register authentication, provide the URL, username, and password, and go ahead and pull that image. Once you do that, we'll actually store that information using the Docker standard so you can click Existing Registry, select the registry that you have logged in to previously, and just go with that. Now, I did that already. I have the NanoServer, Server Core, ASP.NET, and the SDK version of the ASP.NET available to use now in this container host. Now, I can actually create my own image, so I can click to create new. I can select if I have a web application, which is the option that we have so far, but we'll be adding new options in the future. I can select, for example, what kind of application that I have, and we'll be adding more subtypes here for application sources that you can use in the future as well. Today, we have a static web application folder that if you select, as you can see, we'll be using the IIS container image, or you can select the Visual Studio solution. In this case, if I scroll down to the Docker file, it will be provided to me in a second. Now, I have to provide, where is the source of my application, or what is the pattern with my application, on which my application resides. If I check my structure of Visual Studio files here, I have an application called Docker demo. I'm going to select the folder, the C drive, Visual Studio, and then I have a Docker demo. I click OK, and we are going to check what are the projects that are under that folder. And we found that we have a Docker demo folder, or a structure of a solution here. Now, we also give you the option, depending on what your application is running in terms of framework version, what is the framework version you wanna use, and this is going to change the image that we are going to build this application. So if I select 3.5, for example, as you can see, the Docker file down here was changed to that. So we'll be changing the Docker file along the way as you provide more inputs in the Windows Admin Center UI. For this particular project, I'll be using the .NET framework 4.8. In addition to that, if you wanna run a specific script that your application requires you to do, in order to be installed on the server or, in this case, in a container, you can also do that here. When you specify the script, we are going to pass that information in the Docker file as well. That is not a required step. All I have to do now is provide a name for this image, like, for example, my image, and then a tag, like, for example, V2 because I already have one there. I'll click Build, but this process will be running on the background. So I'll go ahead. As you can see, my image is being created here. I already have the version one of this, my web application, and I'm gonna create another image called myImage and then with the V2 tag. This will show up here in a second. As we wait for that, one of the things you probably wanna do as you build a new container image is to validate that this container image runs fine. So I can go ahead and select my image, click Run, and then I have the options to run this container image in this specific container host. So I'm gonna name this myTestContainer. I'm gonna select what are the ports that I wanna open, like, for example, 8008, and then I'm gonna pass on what is the port that I wanna open from the container, because this is using NAT. So we are translating the ports from the host to the ports for the container. Or I can publish all ports that are actually listed inside the Dockerfile in case I did that in the Dockerfile itself. I have memory allocation, CPU count, and actually you can provide all the other parameters that the Docker run command would accept on PowerShell, except that we don't have those in the UI. So you can click the Add option and provide those parameters if you want to. What are the options that you could put here? Like for example, if you need a persistent storage, if you need another network, or if you wanna pass on a environment variable, these are all parameters that Docker run accepts, and you can do that here. I'm gonna close this one, I'll click Run, and the container is now being executed in here. So if I go back to the Containers tab, I can see that now I have two applications running, and one is called My Container, I was running this previously, and then the other one is called My Test Container that I just read. So let's check if the application is actually running properly. I can select the container, and in fact, I can see that the port 8008 is mapped to the port 80 of the container. So let's check if that's working. So I'm gonna say local host, and then I'll pass on 8008, and this is gonna take just a second for ASP.NET to load this out of the container, and there you go, my application is running fine. Now that I checked that my application is running correctly, what I can do is I can push this Container image to an external registry. So if I wanna run this Container image on other hosts, I can then do the same process of pulling this Container image on other hosts. How do I do that? So let's select the image itself, I'm gonna click the push button, and here you have two options. You can either run on the Azure Container Registry, or you can run on a regular registry. What is the difference? The registry option is pretty much similar to the pull option. It's an OCI compliant registry. If you have the URL, username, and password, you'll just provide that information here, and we can go ahead and push. Now, if you do have a Azure account, we streamline that process a little bit. So if I select, for example, the Azure Container Registry here, this is going to use my Azure account and provide me already with a subscription and the registry that I have under that subscription. I can click push, and this will initiate the process of pushing this image into the Azure Container Registry. There you go. So now you have all the new features or all the new functionality of Windows Admin Center with the new containers extension. I hope you like it, and we are looking forward for your feedback. If you need the new functionality or if you need something additional to the new functionality that we created, we'll be happy to hear your feedback. Thank you and see you next time.