SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconWindows edition and build (ProductType 1 = workstation, 2 = DC, 3 = server), RAM
2. 02reconDocker Desktop already installed? version, com.docker.service service
3. 03reconWSL and Virtual Machine Platform already enabled?
4. 04reconsigned-in user, virtualization available (HypervisorPresent True makes VirtualizationFirmwareEnabled unreliable), nested VM?
5. 05reconis a reboot already pending?
6. 06actEnable WSL and Virtual Machine Platformdestructiveverify
7. 07actDownload the installerverify
8. 08actInstall Docker Desktopdestructiveverify
9. 09actAdd the account to docker-users (only if an account is provided)verify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyEnable WSL and Virtual Machine PlatformVerified byGet-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux, VirtualMachinePlatform | Select-Object -ExpandProperty State
2. 02verifyDownload the installerVerified by(Get-AuthenticodeSignature "$env:TEMP\DockerDesktopInstaller.exe").Status
3. 03verifyInstall Docker DesktopVerified by& "$env:ProgramFiles\Docker\Docker\resources\bin\docker.exe" --version
4. 04verifyAdd the account to docker-users (only if an account is provided)Verified byGet-LocalGroupMember -Group docker-users | Select-Object -ExpandProperty Name

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

SEC.05

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.06

Deploy on Servor button

Maintain Docker Desktop (Windows) or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.07

More containers recipes

1. 01Docker EngineDocker Engine + Compose from the official repository, service active, hello-world verified.
2. 02Docker ComposeDocker Compose plugin (docker compose), installed and verified.
3. 03PodmanPodman (daemonless containers, rootless capable), verified.
4. 04PortainerPortainer CE (LTS) Docker management web UI, admin preconfigured.
5. 05k3s (lightweight Kubernetes)Single-node k3s cluster. Destructive: configures networking and a container runtime.