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. 01reconDocker already present?
2. 02reconWSL already enabled (prerequisite)?
3. 03actEnable WSL2destructiveverify
4. 04actInstall Docker Desktopdestructiveverify

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 WSL2Verified bywsl --status
2. 02verifyInstall Docker DesktopVerified bydocker --version

SEC.03

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.04

More containers recipes

1. 01Docker EngineDocker Engine + Compose, service active, hello-world verified.
2. 02Docker ComposeDocker Compose v2 plugin, verified.
3. 03PodmanPodman (rootless containers), verified.
4. 04PortainerPortainer Docker management web UI.
5. 05k3s (lightweight Kubernetes)Single-node k3s cluster. Destructive: configures networking and a container runtime.