Skip to content
35 changes: 35 additions & 0 deletions content/manuals/desktop/setup/install/windows-install.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,41 @@

{{< /accordion >}}

## Verifying system requirements

### WSL: Verification and Setup

Check warning on line 163 in content/manuals/desktop/setup/install/windows-install.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [Docker.HeadingSentenceCase] Use sentence case for headings: 'WSL: Verification and Setup'. Raw Output: {"message": "[Docker.HeadingSentenceCase] Use sentence case for headings: 'WSL: Verification and Setup'.", "location": {"path": "content/manuals/desktop/setup/install/windows-install.md", "range": {"start": {"line": 163, "column": 5}}}, "severity": "WARNING"}

If you have chosen to use WSL, first verify that your installed version meets system requirements by running the following command in your terminal:

```console
wsl --version
```

If version details do not appear, you are likely using the inbox version of WSL. This version does not support modern capabilities and must be updated.

You can update or install WSL using one of the following methods:

#### Option 1: Install or update WSL via the terminal

Check warning on line 175 in content/manuals/desktop/setup/install/windows-install.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [Docker.HeadingLength] Try to keep headings short (< 8 words). Raw Output: {"message": "[Docker.HeadingLength] Try to keep headings short (\u003c 8 words).", "location": {"path": "content/manuals/desktop/setup/install/windows-install.md", "range": {"start": {"line": 175, "column": 6}}}, "severity": "INFO"}

1. Open PowerShell or Windows Command Prompt in administrator mode.
2. Run either the install or update command. You may be prompted to restart your machine. For more information, refer to [Install WSL](https://learn.microsoft.com/en-us/windows/wsl/install).
```console
wsl --install

wsl --update
```

#### Option 2: Install WSL via the MSI package

If Microsoft Store access is blocked due to security policies:
1. Go to the official WSL GitHub Releases page: https://github.com/microsoft/WSL/releases
2. Download the `.msi` installer from the latest stable release (under the Assets drop-down).
3. Run the downloaded installer and follow the setup instructions.

### Adjust installation based on user's administrator access
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite sure about this one.

When in WSL mode, you only activate the Windows Service if you select "Add the *.docker.internal names to the host's /etc/hosts file (Requires password)" from settings.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Craig, I'll double check this on a VM.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that UAC prompt appears in the scenario you mentioned and oops, I missed the part on "com.docker.service is required by Windows containers and Hyper-V backend".

I'll run through installation again tomorrow and fix this. Thanks again @chelnak!

Copy link
Contributor

@karman-docker karman-docker Jun 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chaomonica / @chelnak we can word it something like this:

Title can be "Administrator Privileges and Installation Requirements", since this is generic, it can be outside the "WSL: Verification and Setup" section.

Installing Docker Desktop requires administrator privileges. However, once installed, it can be used without administrative access. Some actions, though, still need elevated permissions. For details, see [Understand permission requirements for Windows].

If your users do not have administrator rights and plan to perform operations that require elevated privileges, be sure to install Docker Desktop using the --always-run-service installer flag. This ensures those actions can still be executed without prompting for UAC elevation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chelnak I've updated the "Administrator Privileges and Installation Requirements" with @karman-docker 's section above and additionally moved this section ahead of the WSL sections to avoid confusion.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you.


Note down if Docker Desktop will be used by non-administrator users. If so, consider using the `--always-run-service` installer flag. This will prevent the `com.docker.service` service from prompting non-administrator users with a User Account Control (UAC) elevation prompt when using Docker Desktop. See [Installer Flags](#installer-flags) for more details.

## Install Docker Desktop on Windows

> [!TIP]
Expand Down
Loading