DEV Community

Cover image for How to Install Docker Desktop on Windows 11 (Step-by-Step Guide for 2026)
InterData
InterData

Posted on

How to Install Docker Desktop on Windows 11 (Step-by-Step Guide for 2026)

#docker

Containerization is a standard practice in modern software development. If you are developing, testing, or deploying applications, Docker is likely already a core part of your daily workflow.

For Windows users, Docker Desktop provides a convenient environment to build, run, and manage containerized applications. When paired with the Windows Subsystem for Linux (WSL 2), Docker Desktop achieves near-native Linux performance and seamless integration.

This step-by-step guide walks you through installing and configuring Docker Desktop on Windows 11, updated with the latest requirements and best practices for 2026.

What Is Docker Desktop?

To understand Docker Desktop, it helps to distinguish the core runtime engine from the desktop application itself.

Docker vs. Docker Desktop

  • Docker Engine: This is the core open-source containerization technology. It includes the Docker daemon (dockerd), the CLI (docker), and APIs used to interact with containers.
  • Docker Desktop: This is a comprehensive, GUI-enabled application that packages Docker Engine, Docker CLI, Docker Compose, and Kubernetes into a single installation. It adds key developer-friendly features, such as:
    • A user-friendly dashboard to manage containers, images, volumes, and networks.
    • One-click Kubernetes orchestration support.
    • Deep integration with WSL 2, allowing you to run commands naturally from both Windows terminals and Linux distributions.
    • Built-in vulnerability scanning and image analysis.

Why Use Docker Desktop on Windows 11?

Using Docker Desktop on Windows 11 simplifies the complex configuration required to run Linux containers natively. In the past, running Docker on Windows meant configuring slow, resource-heavy Hyper-V virtual machines.

Today, Docker Desktop utilizes the lightweight WSL 2 utility VM. This design results in fast startup times, lower CPU consumption, and dynamic memory allocation, allowing unused RAM to return to your host system.

Docker Desktop System Requirements for Windows 11 (Updated June 2026)

Before launching the installation, verify that your computer meets the updated hardware and software specifications.

Supported Windows Versions

Docker Desktop supports the following 64-bit editions of Windows 11:

  • Windows 11 Home
  • Windows 11 Pro
  • Windows 11 Enterprise
  • Windows 11 Education

Note: Microsoft's servicing lifecycle requires you to run Windows 11 version 23H2 (build 22631) or higher to maintain compatibility with current Docker Desktop releases.

Hardware Requirements

Your computer must meet these physical hardware specs:

  • Processor: 64-bit CPU (Intel, AMD, or ARM64 like Snapdragon X platforms) with Second Level Address Translation (SLAT).
  • Virtualization: Hardware virtualization extensions must be enabled in your system's BIOS/UEFI (Intel VT-x or AMD-V).
  • Memory: 4 GB system RAM minimum; 8 GB or more is highly recommended to run containerized services without performance bottlenecks.
  • Storage: At least 6 GB of available disk space, preferably on a solid-state drive (SSD).

Required Software Components

  • WSL 2: WSL version 2.1.5 or higher is required. If you plan to use Docker's Enhanced Container Isolation (ECI), you will need WSL version 2.6 or later.
  • Virtual Machine Platform: This Windows feature must be turned on to support the WSL 2 backend.
  • Microsoft Store Updates: Ensure your Windows Store apps—specifically the Windows Subsystem for Linux app—are updated to their latest versions.

Verify Your System Before Installation

You can inspect your current setup by opening PowerShell and running the following commands:

# Get system hardware details and verify SLAT/Virtualization status
systeminfo

# Check the installed WSL version
wsl --version

# View the status of currently installed Linux distributions
wsl --status
Enter fullscreen mode Exit fullscreen mode

Step 1: Enable Virtualization in BIOS/UEFI

Docker Desktop requires hardware-level virtualization to execute container runtimes.

How to Check Whether Virtualization Is Enabled

  1. Press Ctrl + Shift + Esc to open the Task Manager.
  2. Navigate to the Performance tab and select CPU.
  3. Look for Virtualization in the bottom-right corner. It should read Enabled.

Alternatively, run the following command in PowerShell:

(Get-WmiObject Win32_Processor).VirtualizationFirmwareEnabled
Enter fullscreen mode Exit fullscreen mode

If it returns True, virtualization is enabled. If it returns False, you must turn it on via your system BIOS.

Enable Intel VT-x or AMD-V

If virtualization is disabled, restart your computer and enter your BIOS/UEFI utility (typically by tapping F2, F10, F12, or Del during startup).

  1. Locate the CPU Configuration, Advanced, or Security menu.
  2. Find Intel Virtualization Technology (VT-x) or SVM Mode (AMD-V).
  3. Set the option to Enabled.
  4. Save your changes (usually by pressing F10) and restart Windows.

Verify Virtualization Status

Open the Task Manager once more to confirm that Virtualization is now listed as Enabled.

Step 2: Install or Update WSL 2

WSL 2 lets Windows run a genuine Linux kernel within a lightweight virtual machine, which acts as the execution engine for Docker.

Why Docker Desktop Uses WSL 2

Using the WSL 2 backend brings notable advantages:

  • Performance: Significantly faster file-sharing speeds between Windows and Linux filesystems.
  • Dynamic Resources: WSL 2 allocates CPU and RAM dynamically as Docker demands them, preventing your host machine from running out of system memory.
  • Kernel Integration: Containers run directly on a secure, optimized Linux kernel managed by Microsoft and Docker.

Install WSL 2 via PowerShell

If WSL is not yet installed on your machine, open PowerShell as an Administrator and execute:

wsl --install
Enter fullscreen mode Exit fullscreen mode

This command enables the virtual machine platform, installs the WSL 2 runtime, and downloads the default Ubuntu Linux distribution.

Update WSL to the Latest Version

To avoid compatibility bugs, ensure you are running the latest WSL release:

wsl --update
Enter fullscreen mode Exit fullscreen mode

Verify WSL Installation

Run the following command to check your active WSL version and installed distros:

wsl --version
wsl --list --verbose
Enter fullscreen mode Exit fullscreen mode

Verify that the output displays a WSL version of at least 2.1.5.

Install Ubuntu (Optional but Recommended)

While Docker Desktop manages its own internal WSL distros, having a user-facing Linux distro like Ubuntu lets you run development environments alongside your containers. To install it, run:

wsl --install -d Ubuntu
Enter fullscreen mode Exit fullscreen mode

Step 3: Download Docker Desktop for Windows 11

Download from the Official Docker Website

Always download the installer directly from official sources to ensure you receive a secure and untampered executable.

  1. Visit the official Docker Desktop for Windows installation page.
  2. Click the Docker Desktop for Windows download button to save the installer (typically named Docker Desktop Installer.exe).

Docker Desktop Licensing Overview

Before installing, check which licensing tier matches your profile:

  • Docker Personal (Free): For personal use, educational learning, open-source projects, and small business entities.
  • Small Businesses: Free if your organization has fewer than 250 employees and less than $10 million in annual revenue.
  • Docker Pro, Team, or Business (Paid): Required for commercial use in larger organizations that exceed the small business limits.

Step 4: Install Docker Desktop on Windows 11

Run the Installer

  1. Locate the downloaded Docker Desktop Installer.exe file in your downloads folder.
  2. Double-click to launch the setup.
  3. When the User Account Control (UAC) dialog appears, grant administrator permissions to proceed.

Recommended Installation Settings

During the installation phase, a configuration screen will present two key options:

  • Use WSL 2 instead of Hyper-V (Recommended): Make sure this checkbox is selected. This ensures Docker uses the high-performance WSL 2 backend instead of older legacy virtualization.
  • Add shortcut to desktop: Select this option if you want a quick-launch shortcut on your desktop.

Complete Installation

  1. Click Ok to begin extracting and writing files.
  2. Once the setup displays "Installation Succeeded," click Close and restart to reboot your computer. A system restart is necessary to properly apply configuration changes to the WSL system components.

Step 5: Configure Docker Desktop

Initial Startup Configuration

  1. After Windows restarts, launch Docker Desktop using your desktop shortcut or the Windows Start menu.
  2. Review and accept the Docker Subscription Service Agreement to continue.
  3. Complete the short onboarding survey, or click Skip to head straight to the dashboard.

Enable the WSL 2 Backend

To confirm that Docker Desktop is leveraging your WSL 2 installation:

  1. Click the Gear icon in the top navigation bar of the Docker Desktop UI to open Settings.
  2. Navigate to the General tab.
  3. Verify that Use the WSL 2 based engine is checked. If it is grayed out, your computer's virtual machine platform features might not be fully configured.

Enable WSL Integration

If you want to access your Docker environment directly from your installed Linux distributions (e.g., Ubuntu):

  1. In Settings, navigate to Resources and select WSL Integration.
  2. Toggle the Enable integration with my default WSL distro switch.
  3. Under "Enable integration with additional distros," switch on the toggle next to Ubuntu (or your preferred distribution).
  4. Click Apply & restart to save changes.

Recommended Resource Settings

Because WSL 2 uses dynamic resource allocation, Docker handles CPU and memory consumption automatically. However, to prevent WSL from consuming too much memory during heavy operations, you can optimize your WSL performance.

Create a file named .wslconfig in your Windows user profile directory (C:\Users\<YourUsername>\.wslconfig) and add these configurations:

[wsl2]
memory=8GB        # Limit WSL memory consumption (e.g., to 8GB)
processors=4      # Limit CPU core allocation
autoMemoryReclaim=gradual # Reclaim unused memory from the WSL VM automatically
Enter fullscreen mode Exit fullscreen mode

Note: The autoMemoryReclaim feature is highly recommended as it dynamically releases RAM back to Windows after heavy image-building sessions complete.

Step 6: Verify Docker Installation

With configuration complete, verify that the installation is operational using your favorite terminal (PowerShell, Command Prompt, or Ubuntu WSL).

Check Docker Version

Run this command to check the installed client and server versions:

docker --version
Enter fullscreen mode Exit fullscreen mode

Expected Output:

Docker version 27.x.x, build xxxxxxx
Enter fullscreen mode Exit fullscreen mode

Check Docker Compose

Docker Desktop includes Docker Compose out of the box. Verify its installation with:

docker compose version
Enter fullscreen mode Exit fullscreen mode

Run Your First Container

Test your container runtime by pulling and running the lightweight hello-world test image from Docker Hub:

docker run hello-world
Enter fullscreen mode Exit fullscreen mode

If successful, Docker will download the image, run it inside a temporary container, print a "Hello from Docker!" message to your terminal, and exit.

Verify Running Containers

You can list active and stopped containers to confirm that everything was tracked successfully:

docker ps -a
Enter fullscreen mode Exit fullscreen mode

Test Docker from Ubuntu WSL

Open your Ubuntu WSL terminal and run:

docker version
Enter fullscreen mode Exit fullscreen mode

If your integration settings were applied correctly, you should see the system output without needing to install the Docker daemon separately inside Linux.

Understanding the Docker Desktop Architecture on Windows 11

To get the most out of your installation, it helps to understand how these technologies work together behind the scenes.

┌────────────────────────────────────────────────────────┐
│                      WINDOWS 11                        │
├────────────────────────────┬───────────────────────────┤
│    PowerShell / Cmd        │   WSL 2 (Ubuntu Distro)   │
│   (Interacts with CLI)     │    (Interacts with CLI)   │
└─────────────┬──────────────┴─────────────┬─────────────┘
              │                            │
              └─────────────┬──────────────┘
                            ▼
              ┌────────────────────────────┐
              │    Docker Desktop Engine   │
              │   (WSL 2 Utility Distros)  │
              └────────────────────────────┘
Enter fullscreen mode Exit fullscreen mode

How Docker Uses WSL 2

Docker Desktop runs two lightweight, specialized Linux distributions in the background:

  • docker-desktop-data: Used to store your active containers, pulled images, and persistent volumes.
  • docker-desktop: Used to run the Docker Engine and daemon.

This separation keeps container workloads isolated, protecting your Windows configuration from unexpected errors.

Docker Desktop Components

  • Docker Engine: Runs the core background container processes.
  • Docker CLI: Allows you to interact with the engine using text commands.
  • Docker Compose: Assists in orchestrating multi-container environments using simple .yaml files.
  • Docker Desktop UI: Gives you a graphical look at running services, container resource usage, and application logs.

Why WSL 2 Is Recommended Over Hyper-V

While Hyper-V remains an option, WSL 2 is the preferred backend for modern Windows setups. Under Hyper-V, Windows pre-allocates a fixed block of RAM and CPU to the virtual machine, which makes those resources unavailable to your other Windows apps. WSL 2 allocates memory and CPU resources dynamically based on actual runtime needs, which helps your computer run much cooler and smoother.

Common Docker Desktop Installation Issues and Fixes

If you encounter errors during or after setup, check these common troubleshooting paths.

Error: WSL 2 Is Not Installed

  • Symptoms: Docker Desktop warns that the WSL kernel is missing or outdated.
  • Fix: Open PowerShell as Administrator and run wsl --install followed by wsl --update.

Error: Virtualization Must Be Enabled

  • Symptoms: Docker Desktop reports that hardware-assisted virtualization must be enabled.
  • Fix: Reboot your computer, enter your BIOS settings, and enable Intel VT-x or AMD-V.

Docker Desktop Stuck on "Starting"

  • Symptoms: The status bar remains yellow and the app never reaches the green "running" state.
  • Fix:
    1. Update your WSL kernel: wsl --update.
    2. Restart your WSL service: wsl --shutdown and then launch Docker Desktop again.
    3. Verify that your third-party antivirus software isn't blocking virtual network adapters.

Docker Command Not Found

  • Symptoms: Running docker in PowerShell returns an command recognition error.
  • Fix: Ensure Docker Desktop is actually running. If it is, try restarting your terminal session to refresh your environment variables and PATH settings.

WSL Integration Not Working

  • Symptoms: docker version works in PowerShell but returns "command not found" inside your WSL Ubuntu terminal.
  • Fix: Go to Docker Desktop Settings -> Resources -> WSL Integration and make sure your specific Linux distribution is enabled.

Insufficient Memory or Disk Space

  • Symptoms: Containers crash unexpectedly, or builds fail due to storage errors.
  • Fix:
    • Clean up unused resources by running docker system prune -a --volumes inside your terminal.
    • Limit maximum memory allocation in your .wslconfig file, as shown in Step 5.

Best Practices After Installing Docker Desktop

To maintain a fast and stable development environment, keep these guidelines in mind:

Keep Docker Desktop Updated

Docker frequently releases security patches, bug fixes, and performance improvements. Check for updates regularly through the notification icon in the dashboard, or download the latest installer to apply upgrades over your existing setup.

Use Linux Containers Whenever Possible

Windows containers are supported but have a much larger footprint and run on a more limited ecosystem. Linux containers are the industry standard for production deployments, and they run naturally inside the WSL 2 backend on Windows.

Store Projects Inside WSL

This is the single most important tip for performance on Windows 11: Always store your active project files and source code inside the native WSL filesystem (e.g., /home/username/projects/) rather than mounting folders from your Windows drive (e.g., /mnt/c/Users/...). Accessing files across the Windows-to-Linux boundary is significantly slower than working directly within the Linux partition.

Learn Essential Docker Commands

Familiarize yourself with these core commands to navigate the CLI:

# List local images
docker images

# Pull an image from Docker Hub
docker pull nginx

# Build an image from a local Dockerfile
docker build -t my-app .

# Start a container in detached mode
docker run -d -p 8080:80 --name web nginx

# View container logs
docker logs web

# Stop and remove a container
docker stop web && docker rm web
Enter fullscreen mode Exit fullscreen mode

FAQ: Docker Desktop on Windows 11

Is Docker Desktop Free?

Docker Desktop is free for personal use, education, public open-source projects, and small businesses (defined as having fewer than 250 employees and less than $10 million in annual revenue). Larger organizations require a paid subscription.

Can I Install Docker Desktop on Windows 11 Home?

Yes. Thanks to the WSL 2 backend, Docker Desktop runs on Windows 11 Home with the same features and performance as it does on Windows 11 Pro.

Do I Need Hyper-V?

No. While Docker Desktop can run on top of Hyper-V, using the default WSL 2 backend is the recommended approach for better performance and lower resource usage.

Why Does Docker Require WSL 2?

Containers are native to the Linux kernel. WSL 2 provides a highly optimized Linux kernel directly inside Windows, allowing Docker to run containers natively with low overhead.

Can I Run Kubernetes with Docker Desktop?

Yes. You can enable a single-node Kubernetes cluster directly inside the Docker Desktop settings under the Kubernetes tab.

How Much RAM Does Docker Desktop Need?

A minimum of 4 GB of RAM is required, but 8 GB is highly recommended for standard development work. If you run heavy multi-container stacks, 16 GB is ideal.

How Do I Update Docker Desktop?

You can update Docker Desktop by clicking the Update notification in the UI dashboard, or by downloading and running the latest installer directly over your current installation.

Can I Install Docker Without Docker Desktop?

Yes, you can install the open-source Docker Engine directly inside a WSL 2 Linux distribution. However, you will lose the Docker Desktop GUI, automatic updates, built-in Kubernetes support, and simple Windows-host integration.

Conclusion

Setting up a local container environment is an accessible process. By enabling virtualization, updating WSL 2, and configuring Docker Desktop to use the WSL 2 backend, you can establish a fast, standard-compliant development station on Windows 11.

Now that your setup is complete, you can begin pulling images, writing Dockerfiles, and deploying your containerized applications locally.

Need a High-Performance VPS for Docker Workloads?

Whether you're developing microservices, deploying Docker Compose stacks, hosting containers, or building CI/CD pipelines, your local machine can only take you so far.

InterData VPS provides the ideal environment for running Docker in production:

  • High-performance yet cost-effective VPS plans
  • Latest-generation CPU platforms
  • Ultra-fast NVMe U.2 SSD storage
  • High network throughput for containerized applications
  • Generous bandwidth allocation
  • Full root access and flexible deployment options

👉 Explore InterData VPS plans

Ready to move from local Docker development to production? Start with an InterData VPS and deploy your containers with confidence.

Top comments (0)