Module 6: Deploying and managing Windows and Hyper-V containers
graphical user interface (GUI)
Additionally, keep in mind that containers do not have a _. Based on the characteristics of a container, for example, you will probably not run your accounting package in a container.
software discovery, installation, and inventory
After a provider is installed and imported, you can search, install, and perform an inventory on the software packages with that provider—this process is commonly referred to as _ (SDII).
New-VMSwitch -Name <Virtual Switch Name> -SwitchType <Type>
All containers connect to a virtual switch for network communications. The switch type can be Private, Internal, External, or NAT. To complete this task, type the following Windows PowerShell cmdlet, and then press Enter:
Container image
As modifications are made to a container's file system or registry, these changes are captured in the container's sandbox. The _ will only contain the changes that the installation of the app made, with a layer on top of the container OS image.
every
Docker EE for Windows Server brings the agility, portability, and security benefits of the Docker platform to _ edition(s) of Windows Server 2016.
Datacenter
Docker EE now includes Docker _. It integrates security from the development to production process with container management.
Enterprise Edition (EE)
Docker _ is designed to work with both Linux and Windows operating systems and with various cloud-service environments
Container
Docker components: _ A runtime instance of an image, consisting of the image, its operating environment, and a standard set of instructions.
Image
Docker components: _ A stateless collection of root file system changes in the form of layered file systems that are stacked on one another.
Dockerfile
Docker components: _ A text file that contains the commands that need to run to build a Docker image.
Build
Docker components: _ The process of building Docker images from a Dockerfile and any other files in the directory where the image is being built.
Docker Engine
Docker toolbox tools include: _. This is a lightweight runtime environment for building and running Docker containers. includes an in-host daemon (Linux service) that you communicate with by using the Docker client for building, deploying, and running containers.
Container repository
Each time you make a container image, the container image and its dependencies are stored in a local _. This allows you to reuse the image as many times as you want on the container host.
PowerShellGet
Except for _, all package providers are installed on demand.
Windows Server
For example, _ containers are preferred in scenarios where the OS trusts the apps that it hosts, and all the apps must trust each other. In other words, the host OS and apps are within the same trust boundary.
Containers do not include the OS
How do windows server containers differ from VMs?
nested virtualization
If you are using a Hyper-V virtual machine to run a Hyper-V container, you must enable the _ feature and Hyper-V server role on that virtual machine.
Hyper-V
If you deploy Hyper-V containers, the _ role needs to be installed.
nested virtualization
If you deploy a Windows container host on a Hyper-V VM that is hosting Hyper-V containers, you need to enable _.
New-NetNat -Name ContainerNat -InternalIPInterfaceAddressPrefix "172.16.0.0/12"
If you want to use a virtual switch configured with NAT, you must configure the NAT settings. For example, you can type the following Windows PowerShell command, and then press Enter:
Set-VMProcessor -<VMName Container Host VM> -ExposeVirtualizationExtensions $true
If your container host is a Hyper-V VM, you must enable nested virtualization. Type the following Windows PowerShell command, and then press Enter:
Get-VMNetworkAdapter -VMName <Container Host VM> | Set-VMNetworkAdapter -MacAddressSpoofing On
If your container host is virtualized, you must enable media access control (MAC) address spoofing. For example, you can type the following Windows PowerShell command, and then press Enter:
All changes that are made to a running container are stored in the sandbox.
In Windows Server 2016 containers, which of the following statements best describes a sandbox? A sandbox is a computer that is configured with containers. This can be a physical computer or a virtual computer. A sandbox is the first layer of the container hierarchy. All changes that are made to a running container are stored in the sandbox. A sandbox is a management tool that you can use instead of the Windows PowerShell command-line interface to manage your containers.
containers
In many ways, _ (also referred to as _-based OS virtualization) are the next evolution in virtualization
Hyper-V Container OS images
Nano Server is no longer supported on hardware installs. What is it primarily used for now?
Windows Server
One of the challenges with _ containers is that they share a significant portion of the OS between the base image and the container image. Consequently, if you upgrade the OS in the base image, then you also need to upgrade the container.
NuGet
Package provider for C# packages
DockerProvider
Package provider for Docker Enterprise Edition for Windows Server 2016; combines same features as DockerMsftProvider
MyAlbum
Package provider for discovering photos in your remote file repository and installing them to your local folder
ContainerImage
Package provider for discovering, downloading, and installing Windows container OS images
WSAProvider
Package provider for discovering, installing, and inventorying Windows Server App (WSA) packages—a wrapper for APPX cmdlets
DockerMsftProvider
Package provider for discovering, installing, and updating Docker images
PowerShellGet
Package provider for installing Windows PowerShell modules and scripts from the online gallery
OneGet
PackageManagement (formerly known as _), is a package management aggregator. Although many people commonly assume that PackageManagement is a package provider, this package manager is a unified package management interface component with a set of managed and native APIs, a set of Windows PowerShell cmdlets, and a WMI provider
child
Similar to VMs, Hyper-V containers are the deployed _ partitions.
Multiple tenants Single Tenants Independent lifecycle management
Some common usage scenarios for Hyper-V containers include:
Hosting Stateless Apps Rapid test deployment
Some common usage scenarios for Windows Server containers include:
Docker Engine
Supporting the Docker container is the core of the Docker platform, or the _
sandbox
The _ contents are automatically deleted whenever the container stops.
Docker toolbox
The _ is a collection of Docker platform tools that make building, testing, deploying, and running Docker containers possible.
PackageManagement
The reason many administrators incorrectly assume _ is a package provider is because it includes a minimal set of package providers—basically, the bare minimum needed to discover and install more providers.
Hyper-V
The trust boundary in _ containers provides security-enhanced isolation between the containers on the host, the hypervisor, and the host's other processes. For this reason, _ containers are the preferred virtualization model in multitenant environments.
Docker Engine
This in-host daemon is a lightweight runtime environment that communicates with the Docker client to run commands to build, ship, and run Docker containers. This guarantees that the app always runs the same, regardless of the environment from which it is running.
Overview of Windows Server containers
This is an overview of what?
Sandbox
This layer consists of all the changes made to the container, including file system modifications, registry modifications, or software installations. You can keep or discard these changes as required.
Install the container feature using Server Manager or Powershell
This step to prepare your Windows Server host for containers is not required if you choose to deploy Windows Server containers using Docker Enterprise Edition for Windows Server 2016.
Install-Module DockerProvider -Force Install-Package Docker -ProviderName DockerProvider -Force
To install Docker EE for Windows Server 2016, open the Windows PowerShell console, run the following two commands, and then restart the system:
Hyper-V
To run a Hyper-V container successfully, you must enable the _ server role.
True
TorF? If you run more than one container in a Hyper-V virtual machine, then those containers share the virtual machine's kernel.
True
TorF? Before server 2016, it was not possible to use the Windows Server platform to host the Docker Engine, without adding an additional layer of virtualization.
True
TorF? Docker Enterprise Edition (EE) available for Windows Server 2016 at no cost
False, it uses the same Docker Command Line Interpreter, API, image format, and Docker registry services.
TorF? Docker works very differently on Windows Server than it does on Linux
True
TorF? One of the key differences between a container and a VM is that containers don't have virtual hard disks.
True, There is currently no method to present the appropriate kernel to a container from another platform.
TorF? Windows containers require a Windows Docker host, and Linux containers require a Linux Docker host.
Windows 10 insider releases
What Host OS doesnt support WINDOWS SERVER containers, but supports Hyper-V containers?
Windows Server 2016 Desktop Experience, Core, and Windows 10 Insider releases. Nano Server Image.
What Host OS's support Hyper-V containers? What OS Image does the image need to be?
Windows Server 2016 Desktop Experience And Core Server Core Image
What Host OS's support WINDOWS SERVER containers? What OS Image does the image need to be?
Enable Hyper-V role Enable Nested Virtualization Configure Virtual Processors
What additional steps are needed when preparing your windows server host for Hyper-V containers?
Windows Server containers Hyper-V containers
What are the 2 different types of containers?
Install the container feature* Create a virtual switch Configure NAT settings Configure MAC address spoofing
What are the 4 steps for preparing your windows server host for containers?
Container host
What container element consists of the physical or virtual computer that is configured with the Windows containers feature. This can run one or more Windows containers.
Hyper-V containers, because they are more isolated.
What type of container is the most secure?
Windows server container
What type of container would you run if you trust all of the apps that are running on the host
package provider
When deploying containers, you begin with a base image, such as a Windows Server Core image. Because base images are not included with Windows Server 2016, you need to use a _ to retrieve and manage the base images for your container deployments.
One common scenario is where one or more of the apps that you want to host in a Windows container have a dependency on the OS version level or the patch level of the underlying container host.
When would Hyper-V containers might be useful even in a single-tenant environment?
Container OS image.
While containers are made from images, the _ is the first layer in potentially multiple image layers that make up a container. The _ provides the OS environment, and it is immutable.
runtimes
Windows Server 2016 supports two different types of containers (or _ ), each offering different degrees of isolation with different requirements
layered
Windows Server containers are an ideal way to deploy custom apps, because you can create packages by using a _ approach to building a deployable app.
Install-WindowsFeature Hyper-V
You can Enable the Hyper-V role by using Server Manager or by using the _ Windows PowerShell cmdlet. This is required only if you deploy Hyper-V containers.
Find-PackageProvider
You can also use the Windows PowerShell cmdlet _ to list all the package providers available for container installation.
Docker
You can create and manage Windows containers by using either the _ tool set or Windows PowerShell.
Install-WindowsFeature Containers
You can install container feature by using Server Manager, or you can type the following Windows PowerShell cmdlet, and then press Enter:
stateless
You should ensure that the apps that you deploy in a container on a Windows Server 2016 host are _. ( _apps do not store any state data in their containers.)
Containers
_ are a way to wrap up an application into its own isolated box. For the application in its _, it has no knowledge of any other applications or processes that exist outside of its box. Everything the application depends on to run successfully also lives inside this _. Wherever the box may move, the application will always be satisfied because it is bundled up with everything it needs to run.
stateless web apps that do not have a GUI
_ are the most likely candidates for using Windows container technologies in Windows Server 2016.
Hyper-V
_ container enables you to have different versions of base images that allow you to simultaneously host an OS in the container image. This is helpful for enterprises that want to have independent lifecycle management for patching, updating, and compliance.
Windows Server Hyper-V
_ container hosts must have the Windows OS installed to drive C. This restriction does not apply if you deploy only _ containers.
Docker
_ containers are based on open standards that allow containers to run on all major Linux distributions and Microsoft operating systems with support for every infrastructure. Because they are not tied to any specific infrastructure, _ containers can run on any computer, on any infrastructure, and in any cloud.
Hyper-V Windows Server
_ containers are less efficient in startup times and density than _ containers, but they provide the isolation required to allow untrusted apps to run on the same host.
Hyper-V
_ containers do not share the OS kernel with the container host
Hyper‑V Windows Server
_ containers encapsulate each container in a lightweight VM, whereas _ containers achieve isolation through namespace and process isolation.
Docker
_ containers have similar resource isolation and allocation benefits as VMs, but they use a different architectural approach that allows them to be more portable and efficient.
Hyper-V
_ containers provide the required components for the tenants, but they also ensure that one tenant's application cannot interfere with other applications.
Windows Server
_ containers share the OS kernel with the container host and with all other containers that run on the host.
Docker EE
_ for Windows Server 2016 provides the following features and benefits: It is available for all Windows Server 2016 customers at no additional cost. •Lightweight containers start up fast and optimally use system resources. •Container isolation helps to eliminate conflicts of dissimilar versions of IIS/.NET by coexisting on a single system. •It utilizes new base container images such as Windows Server Core and Nano Server.
Docker EE
_ for Windows Server 2016 provides the following features and benefits: •It provides a consistent user experience because it has the same commands as Docker for Linux. •Users can manage and secure containerized Windows applications in the same cluster as Linux applications. •Subscription tiers give Windows apps the same advanced container management features as Linux- based apps for image scanning, overlay networking, and Secrets management. •It adds isolation properties with Hyper-V containers selected at runtime.
Docker
_ is a collection of open-source tools, solutions, and cloud-based services that provide a common model for packaging (or containerizing), app code into a standardized unit for software development.
PackageManagement
_ is the unified interface for supporting software discovery, installation, and inventory (SDII). At the core, it manages the loading and multiplexing of plugin providers and provides isolation for each of them
•They run an OS. •They support a file system. •You can access them across a network, like any other physical machine or VM.
containers are similar to VMs because:
Set-VMProcessor -<VMName Container Host VM> -Count 2
f the container host is a Hyper-V VM, you must configure at least two virtual processors. You can type the following Windows PowerShell command, and then press Enter:
Docker container
is software wrapped in a complete file system that includes everything it needs to run: code, runtime, system tools, and system libraries, or anything you can install on a server.
Windows PowerShell Docker
it is important to understand that you can manage containers by using either _ , or the open source _ platform.
Windows Server containers
provides a faster startup experience, it does not provide complete isolation of the containers.
Windows Server container
usage scenario to its associated Windows container: Rapid test deployment
Windows Server container
usage scenario to its associated Windows container: Hosting stateless apps
Hyper-V container
usage scenario to its associated Windows container: Independent lifecycle management
Hyper-V container
usage scenario to its associated Windows container: Multiple tenants
Hyper-V container
usage scenario to its associated Windows container: Single tenants
Hyper-V container
what type of container would be best if trying to isolate app or the host