Study guide
8.5 Managing Container Instances & Linux Containers with WSL
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
8.5 Managing Container Instances & Linux Containers with WSL
Key Takeaways Explain This Topic AI
Data written to a container's writable layer is destroyed on removal, so persistent state requires a volume or bind mount rather than the container filesystem.
Production instances should be constrained with --cpus, --memory, and --restart unless-stopped, and can be forced into Hyper-V isolation per instance with --isolation hyperv.
Kubernetes nodes run containerd, not the Docker Engine, so container instances on an AKS Hybrid worker node must be inspected with crictl or ctr rather than docker ps.
A Windows Server host cannot natively execute Linux container images; WSL 2 supplies a real Linux kernel in a lightweight utility VM, and the deprecated LCOW feature is no longer the supported path.
WSL 2 requires the Virtual Machine Platform optional component and hardware virtualization, so a virtualized Windows Server host must have nested virtualization exposed before WSL 2 will start.
Last updated: August 2026
Managing Container Instances & Linux Containers with WSL
Building an image is only the first half of the container skill measured on AZ-800. The rest is operational. This section covers the day-to-day half: starting, inspecting, constraining, and removing running instances, and running Linux containers on a Windows Server host. Attaching those instances to the right network and handing orchestration to Kubernetes are covered in section 8.6.
1. Managing Container Instances
A container image is an immutable template; a container instance is a running (or stopped) execution of that template. On a Windows Server container host you drive instances either through the Docker CLI or, on a containerd-only host, through ctr and crictl .
Instance Lifecycle With the Docker CLI # Run detached, name the instance, publish host port 8080 to container port 80
- docker run -d --name web01 -p 8080:80 --isolation=process `
- mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2022
- # List running instances; -a also shows stopped ones
- docker ps
- docker ps -a
- # Lifecycle verbs
- docker stop web01 # graceful shutdown, then SIGKILL after the grace period
- docker start web01
- docker restart web01
- docker rm web01 # must be stopped first, or use -f to force
- # Inspect a running instance
- docker logs web01 --tail 50 --follow
- docker stats web01 # live CPU, memory, network and I/O counters
- docker inspect web01 # full JSON configuration, including network settings
- docker exec -it web01 powershell.exe # interactive shell inside the instance
Important
Anything written inside a container's writable layer is destroyed when the instance is removed. Data that must survive docker rm has to live on a volume or a bind mount : docker run -v C:\HostData:C:\AppData ... .
Constraining Instance Resources
Container instances share the host kernel and, by default, compete freely for host resources. Production hosts should always constrain them:
- Flag Effect
- -cpus 2 Limits the instance to two logical processors' worth of CPU
- -cpu-shares 512 Relative CPU weight under contention (default is 1024)
- -memory 2g Hard memory ceiling; the instance is terminated if it exceeds it
- -restart unless-stopped Restarts the instance automatically after a host reboot or a crash
--isolation hyperv Runs this instance in Hyper-V isolation regardless of the host default docker run -d --name api01 --cpus 2 --memory 4g --restart unless-stopped `
- -isolation hyperv contoso/orders-api:2.4
- Managing Instances Under containerd
Modern Windows Server container hosts and every Kubernetes node run containerd rather than the Docker Engine. The equivalent tooling is ctr for raw containerd operations and crictl for Kubernetes CRI-level operations: ctr --namespace default containers list
ctr --namespace default tasks list
- crictl ps # running containers known to the CRI
- crictl pods # pod sandboxes on this node
- crictl logs <container-id>
- crictl stats
Tip
docker ps will not show containers created by Kubernetes on a containerd node. When troubleshooting an AKS Hybrid worker node, reach for crictl , not docker .
2. Running Linux Containers on Windows Server With WSL
Windows Server containers share the host kernel, which means a Windows Server host cannot natively execute a Linux container image — a Linux container needs a Linux kernel. The supported way to provide one on Windows Server is the Windows Subsystem for Linux (WSL 2) , which runs a genuine Linux kernel inside a lightweight, Microsoft-managed utility virtual machine.
Note
The older "Linux Containers on Windows" (LCOW) preview feature has been deprecated . WSL 2 is the current path for Linux container workloads on a Windows Server host.
Enabling WSL 2 on Windows Server
WSL 2 depends on the Virtual Machine Platform optional component, because the utility VM is a Hyper-V construct. # Enable the two required optional components
- Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux -NoRestart
- Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -NoRestart
- Restart-Computer
- # Install WSL and a default distribution, then confirm the version in use
- wsl --install
- wsl --list --online
- wsl --install -d Ubuntu
- wsl --set-default-version 2
- wsl --list --verbose
Key constraints the exam expects you to recognise:
WSL 2 requires hardware virtualization. If the Windows Server itself is a virtual machine, nested virtualization must be enabled on that VM with Set-VMProcessor -VMName <name> -ExposeVirtualizationExtensions $true before WSL 2 will start.
WSL 1 will not do. WSL 1 translates Linux syscalls rather than running a Linux kernel, so it cannot host Linux containers. Confirm VERSION 2 in wsl --list --verbose .
Windows containers and Linux containers on the same host run in separate runtimes ; a single Docker daemon on Windows Server does not run both simultaneously in mixed mode.