Wac tooling

virtualization/windowscontainers/TOC.md

@@ -31,6 +31,13 @@
 ### [Run your first Linux container](quick-start/quick-start-windows-10-linux.md)
 ## Use containers with the Windows Insider program
 ### [Overview](deploy-containers/insider-overview.md)
+## Windows Admin Center tooling
+### [Containers extension overview](WAC-tooling/WAC-extension.md)
+### [Managing container images with Windows Admin Center](WAC-tooling/WAC-Manage.md)
+### [Running containers with with Windows Admin Center](WAC-tooling/WAC-Containers.md)
+### [Creating new container images with Windows Admin Center](WAC-tooling/WAC-Images.md)
+### [Managing Azure Container Registry with with Windows Admin Center](WAC-tooling/WAC-ACR.md)
+### [Managing Azure Container Instance with Windows Admin Center](WAC-tooling/WAC-ACI.md)
 
 # Concepts
 ## Windows Container Essentials

virtualization/windowscontainers/WAC-tooling/WAC-ACI.md

@@ -0,0 +1,32 @@
+---
+title: Manage Azure Container Instances on Windows Admin Center
+description: Azure Container Instances on Windows Admin Center
+keywords: docker, containers, Windows Admin Center
+author: viniap
+ms.author: viniap
+ms.date: 12/24/2020
+ms.topic: Tutorials
+ms.assetid: bb9bfbe0-5bdc-4984-912f-9c93ea67105f
+---
+# Manage Azure Container Instances using Windows Admin Center
+
+This topic describes how to manage Azure Container Instances (ACI) using Windows Admin Center. Azure Container Instances is a solution for any scenario that can operate in isolated containers, without orchestration.
+
+>[!Note]
+>An Azure subscription is required to run the steps in this tutorial. For more information on how to connect your Windows Admin Center instance to Azure, check out the [documentation](https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/azure-integration).
+
+Windows Admin Center allows you to perform basic management of Azure Container Instances, including listing the existing container instances, starting and stopping an instance, removing instances, and opening the Azure Portal for advanced management.
+
+![WAC-ACI](./media/WAC-ACI.png)
+
+With the container instanes listed, you can perform the following operations:
+
+- Start: To start an already existing instance that is currently stopped.
+- End: To stop a running instance.
+- Delete: To delete an instance. This is irreversible and will remove any configuration made to the instance.
+- Manage in Azure: This will open the Azure Portal pane to manage the selected container instance on a new browser tab.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Manage Azure Container Registry on Windows Admin Center](./WAC-ACR.md)

virtualization/windowscontainers/WAC-tooling/WAC-ACR.md

@@ -0,0 +1,49 @@
+---
+title: Manage Azure Container Registry on Windows Admin Center
+description: Azure Container Registry on Windows Admin Center
+keywords: docker, containers, Windows Admin Center
+author: viniap
+ms.author: viniap
+ms.date: 12/24/2020
+ms.topic: Tutorials
+ms.assetid: bb9bfbe0-5bdc-4984-912f-9c93ea67105f
+---
+# Manage Azure Container Registry using Windows Admin Center
+
+This topic describes how to manage Azure Container Registry (ACR) using Windows Admin Center. Azure Container Registry allows you to build, store, and manage container images and artifacts in a private registry for all types of container deployments. 
+
+>[!Note]
+>An Azure subscription is required to run the steps in this tutorial. For more information on how to connect your Windows Admin Center instance to Azure, check out the [documentation](https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/azure-integration).
+
+Windows Admin Center allows you to perform basic management of Azure Container Registry, including listing registries and images, creating new registries, removing images, pulling images to your container host, and starting new containers on Azure Container Instance from images stored in Azure Container Registry.
+
+Managing ACR from Windows Admin Center also allows you to prepare the Azure location on which you can push images directly from the Images tab under Container host. To get started, open your Windows Admin Center instance, target your container host, and open the Azure Container Registry tab on the Containers extension under Azure.
+
+![WAC-ACR](./media/WAC-ACR.png)
+
+## Managing registries and images
+
+To create a new registry, on the Azure Container Registry menu click Create New Registry:
+
+![WAC-ACRNew](./media/WAC-ACRNew.png)
+
+On the Create new Registry menu, select the subscription you want to use to create a new registry. Select the Resource Group you want to allocate the registry. Next, provide a registry name, location and SKU. More information on pricing and features on each SKU can be fund in the [ACR documentation](https://docs.microsoft.com/en-us/azure/container-registry/). Click Create to create the new registry. Once completed Windows Admin Center will inform if the operation completed sucessfully and you'll see the new registry listed.
+
+Once registries and images are listed you can remove an existing image or pull it to the container host for local use. To pull an image, select the image you want to pull and click Pull Image:
+
+![WAC-ACRPull](./media/WAC-ACRPull.png)
+
+Once the pull process completes, Windows Admin Center will notify you and the image will be available for use on the Images tab under Container Host.
+
+Finally, you can run a new Container based on an image hosted on ACR. To get started, select the image you want to run and click Run Instance:
+
+![WAC-ACRRun](./media/WAC-ACRRun.png)
+
+On the Run Instance menu, you need to provide a container name, which subscription to use, and the resource group and location you want to run this instance.
+
+Next, you can provide the CPU and Memory allocation for this instance as well as the port you want to open, if needed. Click Create and Windows Admin Center wil send the command to Azure to run the instance. You can check the status of the container instance on the Azure Container Instance tab.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Manage Azure Container Instance on Windows Admin Center](./WAC-ACI.md)

virtualization/windowscontainers/WAC-tooling/WAC-Containers.md

@@ -0,0 +1,36 @@
+---
+title: Run containers on Windows Admin Center
+description: Container images on Windows Admin Center
+keywords: docker, containers, Windows Admin Center
+author: viniap
+ms.author: viniap
+ms.date: 12/23/2020
+ms.topic: Tutorials
+ms.assetid: bb9bfbe0-5bdc-4984-912f-9c93ea67105f
+---
+# Run new Containers using Windows Admin Center
+
+Windows Admin Center helps you containers locally on your container host. Using your Windows Admin Center instance with the Containers extension installed, open the container host you want to manage and select the Containers extension on the left-hand side. Click the Images Tab inside under Container Host.
+
+![WAC-Images](./media/WAC-Images.png)
+
+Select the image you want to run and click Run.
+
+![WAC-RunContainers](./media/WAC-RunContainers.png)
+
+On the Run menu you can specify the container related configuration:
+
+- Container name: This is an optional input. You can provide a container name to help you track the container you created - otherwise Docker will provide a generic name to it.
+- Isolation type: You can choose to use hypervisor instead of the default process isolation. For more information on isolation modes for Windows Containers, check out the [documentation](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container).
+- Publish ports: By default, Windows containers use NAT for networking mode. This means a port on the container host will be mapped to the container. This option allows to specify that mapping.
+- Memory and cpu allocation: You can specify how much memory and how many CPUs a container should be able to use. This option does not allocate the assigned memory or CPU to the container. Rather, this options specifies the maximuns a container will be able to allocate.
+- Add: You can also append Docker run parameters that are not in the UI, such as -v for persistent volume. For more information on available Docker run parameters, check out the [documentation](https://docs.docker.com/engine/reference/commandline/run/).
+
+Once you specified the configuration for the container, click Run. You can check out the status of the running containers on the Containers tab:
+
+![WAC-Containers](./media/WAC-Containers.png)
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Manage Azure Container Registry on Windows Admin Center](./WAC-ACR.md)

virtualization/windowscontainers/WAC-tooling/WAC-Images.md

@@ -0,0 +1,45 @@
+---
+title: Create container images on Windows Admin Center
+description: Container images on Windows Admin Center
+keywords: docker, containers, Windows Admin Center
+author: viniap
+ms.author: viniap
+ms.date: 12/23/2020
+ms.topic: Tutorials
+ms.assetid: bb9bfbe0-5bdc-4984-912f-9c93ea67105f
+---
+# Create new Container images on Windows Admin Center
+
+This topic describes how to create new container images using Windows Admin Center. Container images are used to create new containers on Windows machines or other cloud services, such as Azure Kubernetes Service. For more information on Windows images, check out the [Container images overview](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/#container-images).
+
+## Create new container images
+
+When working with containers, you will find yourself writing instructions to Docker on how your container image works so Docker can create a new container image based on these instructions. These instructions are saved on a file called "dockerfile" which is saved on the same folder on which your application resides. 
+
+Windows Admin Center can drastically reduce the overhead of writing these dockerfiles or even completely remove the need to manually write down these files. To get start, on the Containers extension select the option Create New on the Images tab.
+
+![WAC-CreateNewContainer](./media/WAC-CreateNew.png)
+
+The Create new functionality allows for different options while creating a new container image:
+
+- Existing Docker File: This option allows you to rebuild a new container image based on an existing dockerfile. This is very useful when you need to make small changes to an existing dockerfile or simply re-run the container creation to catch an application update.
+- IIS Web Application/Static Web Application Folder: This option will create a new container image using the IIS base image and copy the content of a folder to the container image to add it as a web site. No framework is added on this option.
+- IIS Web Application/Visual Studio Solution(ASP.Net): This option can be used to create a new container image based on an existing Visual Studio Solution. This option will use a multi-image stage approac to stage the application, compile the necessary binaries and store only the necessary assets on the final image. The ASP.Net container image will be used as base image. This option will also ask for the folder on which the Visual Studio resides and will list the existing projects for you to select which one you'd like to containerize.
+- IIS Web Application/Web Deploy (Exported Zip file): This option an be used to create a container image from the artifacts exported from a running server. You can use Web Deploy to expert the application into a Zip file and use Windows Admin Center to create a new container image based on the exported Zip file. The ASP.Net container image wil ne used as base image.
+
+Once you select the initial option of which type of appliation you want to containerize, you can select common options to finalize the creation of your image:
+
+- Framework version: Both the Visual Studio Solution and Web Deploy options will use the ASP.Net image as base for your container image. However, you can select which version of the .Net Framework you want to use in order to accomodate your application.
+- Additional scripts to run: This option allows you to select a PowerShell script to be used at build time. Windows Admin Center will add an instruction to the dockerfile to copy the .PS1 file to the container image and run this script when the container image is created. This can be very helpful if your application requires you to run any additional steps that are not contemplated in the application itself.
+- Image Name: The final image name to be used. This can be changed later when you push the image to a container registry.
+- Image tag: This is used to differentiate multiple versions of the same image. Provide a identifier so your image is properly tagged.
+
+Once you have all the options for your container image selected, you can review the dockerfile. You can also edit the dockerfile by hand if necessary. This dockerfile will be saved on the location of the application you specified in the earlier step. 
+
+>[!Note]
+>If a dockerfile exists in the location of the application you are trying to containerize, Windows Admin Center will replace that file with the new one it just created.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Run containers on Windows Admin Center](./WAC-Containers.md)

virtualization/windowscontainers/WAC-tooling/WAC-Manage.md

@@ -0,0 +1,40 @@
+---
+title: Manage container images on Windows Admin Center
+description: Container images on Windows Admin Center
+keywords: docker, containers, Windows Admin Center
+author: viniap
+ms.author: viniap
+ms.date: 12/23/2020
+ms.topic: Tutorials
+ms.assetid: bb9bfbe0-5bdc-4984-912f-9c93ea67105f
+---
+# Manage Container images on Windows Admin Center
+
+This topic describes how to manage container images on Windows Admin Center. Container images are used to create new containers on Windows machines or other cloud services, such as Azure Kubernetes Service. For more information on Windows images, check out the [Container images overview](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/#container-images).
+
+## Pull container images
+
+After deploying a container host, the next loggical action is to pull (or download) container images so new containers can be created from said images. You can use Windows Admin Center to pull new container images by opening the Containers extension on your targeted container host, selecting Images on the left-hand side menu under Container Host and clicking Pull.
+
+![WAC-Pull](./media/WAC-Pull.png)
+
+On the Pull menu you can provide the repository and tag for the image you want to pull. You can also select the option to pull all tagged images on that repository.
+
+If the image you want to pull is on a private repository you can provide the username and passoword to authenticate against that repository. If your repository is hosted on Azure Container Registry you can use the native Azure authentication on Windows Admin Center to access the image. This requires the Windows Admin Center instance to be connected to Azure and authenticated with your Azure account. For more information on how to connect a Windows Admin Center instance to Azure, check out the [documentation](https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/azure-integration).
+
+If you are not certain which image to pull, Windows Admin Center also provides a list of common images available. You can expend the Common Windows images tab to see a list of base images that are commonly pulled. Select the image you want to pull and Windows Admin Center will fill out the repository and tag fields.
+
+## Push container images
+
+Once you have your own container image created, it's a good practice to push that image to a centralized repository to allow other container hosts or cloud services to pull the image.
+
+On the Images tab in the Containers extension of Windows Admin Center, select the image you wan to push and click Push.
+
+![WAC-Push](./media/WAC-Push.png)
+
+On the Push menu, you can change the image name and tag before pushing (uploading) it and select to either a generic reposiroty or a repository on Azure Container Registry. For a generic repository, you will need to provide a username and password. For Azure Container Registry, you can use the integrated authentication on Windows Admin Center. For Azure, you can also select which subscription and registry you want to push the image to.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Create new containers on Windows Admin Center](./WAC-Images.md) 

virtualization/windowscontainers/WAC-tooling/WAC-extension.md

@@ -0,0 +1,27 @@
+---
+title: Configure Containers extesion on Windows Admin Center
+description: Container extension on Windows Admin Center
+keywords: docker, containers, Windows Admin Center
+author: viniap
+ms.author: viniap
+ms.date: 12/23/2020
+ms.topic: Tutorials
+ms.assetid: bb9bfbe0-5bdc-4984-912f-9c93ea67105f
+---
+# Configure Containers extesion on Windows Admin Center
+
+This topic describes how to configure the Containers extension on Windows Admin Center. For more information on how to install and configure Windows Admin Center as well as how to target remote serser, check out the [Windows Admin Center documentation](http://aka.ms/wacdocs).
+
+## Install the Containers extesion on Windows Admin Center
+
+On your Windows Admin Center instance click on the Settings button in the top-right. On the left-hand side menu, under Gateway, select Extensions.
+On the Available extensions tab, look for the Containers extension.
+
+![WAC-Extension](./media/WAC-Extension.png)
+
+Select the Containers extension from the list and click Install. Windows Admin Center will refresh and once completed the extension will show up under the Installed extensions tab.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Manage container images on Windows Admin Center](./WAC-Manage.md)

virtualization/windowscontainers/quick-start/run-your-first-container.md

@@ -83,6 +83,28 @@ For this simple example, a ‘Hello World’ container image will be created and
    ```
    The result is that Docker created a container from the 'HelloWorld' image, Docker started an instance of cmd.exe in the container, and the cmd.exe read our file and output the contents to the shell. As the final step, Docker stopped and removed the container.
 
+## Run a Windows container using Windows Admin Center
+
+Windows Admin Center provides a User Interface (UI) that can be used to run containers locally. Using your Windows Admin Center instance with the Containers extension installed, open the container host you want to manage and select the Containers extension on the left side. Click the Images Tab inside the Container extension under Container Host.
+
+![WAC-Images](./media/WAC-Images.png)
+
+If your host doesn't have a base container image, you can click the Pull option:
+
+![WAC-Pull.png](./media/WAC-Pull.png)
+
+On the Pull menu, you can provide the image URL and tag. If you are not certain which image to pull, Windows Admin Center provides a list of common images from Microsoft. You can also provide the credentials to pull an image from a private repository, if necessary. Once you fill out the necessary information, you can click Pull. Windows Admin Center will start the pull process on the container host. After the download is completed you should see the new image on the Images tab.
+
+Select the image you want to run and click Run.
+
+![WAC-RunContainers](./media/WAC-RunContainers.png)
+
+On the Run menu you can specify the container related configuration, such as container name, isolation type, which ports to publish, and memory and cpu allocation. Additionally, you can append Docker run commands that are not in the UI, such as -v for persistent volume. For more information on available Docker run parameters, check out the [documentation](https://docs.docker.com/engine/reference/commandline/run/).
+
+Once you specified the configuration for the container, click Run. You can check out the status of the running containers on the Containers tab:
+
+![WAC-Containers](./media/WAC-Containers.png)
+
 ## Next steps
 
 > [!div class="nextstepaction"]