Container images that are based on nano server must be run as hyper-v containers.
GSP153 Show
OverviewContainer virtualization is a fast evolving technology, which aims to simplify the deployment and management of distributed applications. When people discuss containers, they usually mean Linux-based containers. This makes sense, because native Linux kernel features like cgroups introduced the idea of resource isolation, eventually leading to containers as we know them today. Until recently, only Linux processes could be containerized, but Microsoft introduced support for Windows-based containers in Windows Server 2016 and Windows 10. You can take an existing Windows application, containerize it using Docker, and run it as an isolated container on Windows. There are two flavors of Windows containers: Windows Server and Hyper-V. You can build Windows containers on either the microsoft/windowsservercore and microsoft/nanoserver base images. You can read more about Windows containers in the Microsoft Windows containersdocumentation. Google Cloud provides container-optimized VM images on which to run containers on Compute Engine. There is also a Windows VM image for containers. It comes with Docker, microsoft/windowsservercore, and microsoft/nanoserver base images installed. In this lab you will create a container app and deploy the container app to Compute Engine. What you'll learn
Setup and requirementsBefore you click the Start Lab buttonRead these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources will be made available to you. This hands-on lab lets you do the lab activities yourself in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials that you use to sign in and access Google Cloud for the duration of the lab. To complete this lab, you need:
How to start your lab and sign in to the Google Cloud Console
After a few moments, the Cloud Console opens in this tab. Note: You can view the menu with a list of Google Cloud Products and Services by clicking the Navigation menu at the top-left.Task 1. RDP into the Windows VM
You'll be asked to either downlowd a Chrome RDP Extension or download the RDP file in order to connect.
Once inside the Windows VM, you'll notice that it's a bare-minimum OS with minimal UI. Note: If the command line window is not open, open it by going to Task Manager:Ctrl + Alt + Delete and choose Task Manager. Then, go to File > Run new task > cmd .
Output: REPOSITORY TAG IMAGE ID mcr.microsoft.com/windows/servercore ltsc2019 29a2c2cb7e4dCopy and paste with the RDP clientOnce you are securely logged into your instance, you may find yourself copying and pasting commands from the lab manual. To paste, hold the CTRL-V keys (if you are a Mac user, using CMND-V will not work.) If you are in a Powershell window, be sure that you have clicked into the window or else the paste shortcut won't work. If you are pasting into putty, right click. Task 2. Create a Windows container appFor the app inside the Windows container, use an IIS Web Server. IIS has an image for Windows Server 2019. You can use the image as is and it will serve the default IIS page, but fot this lab, do something more interesting and have IIS serve a page you define. Your folder and file structure should look like: C:\my-windows-app>dir /s /b C:\my-windows-app\content C:\my-windows-app\Dockerfile C:\my-windows-app\content\index.html
Windows containers are cool!
This is the page IIS will serve. Task 3. Build Docker image
You're using the IIS Container image version compatible with Windows Server 2019.
Once the Docker image is built, you can see it along with its IIS dependency: docker imagesSample output: REPOSITORY TAG gcr.io/dotnet-atamel/iis-site-windows latest mcr.microsoft.com/windows/servercore/iis windowsservercore-ltsc2019 mcr.microsoft.com/windows/servercore ltsc2019Click Check my progress below to verify you're on track in this lab. Build Docker imageTask 4. Run the Windows containerYou're now ready to run the Windows container.
Sample output: CONTAINER ID IMAGE 3d7c71a258ce gcr.io/dotnet-atamel/iis-site-windowsTo see the web page, go to the External IP column of Compute Engine instance and simply open it with HTTP in the browser: Task 5. Cleanup
When you are done with experimenting with Windows containers, it is a good idea to either stop or delete the VM you created.
Congratulations!What was covered
Finish your questThis self-paced lab is part of the Windows on Google Cloud quest. A quest is a series of related labs that form a learning path. Completing this quest earns you a badge to recognize your achievement. You can make your badge or badges public and link to them in your online resume or social media account. Enroll or any quest that contains this lab and get immediate completion credit. See the Google Cloud Skills Boost catalog to see all available quests. Take your next labContinue your quest with Install and Use Cloud Tools for PowerShell, or check out these suggestions:
Next steps
Google Cloud training and certification...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies. Manual last updated October 3, 2022 Lab last tested May 19, 2022 Copyright 2022 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated. Does Docker require HyperDocker requires that the Hyper-V feature is enabled, so if necessary will ask you to enable it and restart. Click OK for Docker to enable Hyper-V and restart your system.
Can HyperWith Hyper-V isolation, multiple container instances run concurrently on a host; however, each container runs inside of a highly optimized virtual machine and effectively gets its own kernel. The presence of the virtual machine provides hardware-level isolation between each container as well as the container host.
Why would you want to use HyperSince Hyper-V containers provide much greater isolation between running containers, this allows for a much-improved security stance when compared to simply running traditional Windows Server containers.
How are Windows containers different from HyperAlthough Windows Server containers and Hyper-V containers do the same thing and are managed the same way, the level of isolation they provide is different. Windows Server containers share the underlying OS kernel, which makes them smaller than VMs because they don't each need a copy of the OS.
|