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.
- 01reconDocker Desktop already installed? version
- 02reconarchitecture (arm64/amd64), recent macOS, RAM ≥ 4 GB, free disk, console user (root = nobody signed in)
- 03actDownload Docker.dmgverify
- 04actMount the imageverify
- 05actInstall Docker Desktopverify
- 06actUnmount the imageverify
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.
- 01verifyDownload Docker.dmgVerified by
hdiutil imageinfo /var/tmp/Docker.dmg | grep -m1 Format - 02verifyMount the imageVerified by
test -x /Volumes/Docker/Docker.app/Contents/MacOS/install && echo ok - 03verifyInstall Docker DesktopVerified by
codesign --verify /Applications/Docker.app && echo ok - 04verifyUnmount the imageVerified by
test -d /Volumes/Docker && echo mounted || echo ok
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
The daemon only starts when the user signs in (Docker Desktop is an app): report it. Commercial use requires a Docker license. Do not remove an existing installation.
SEC.04
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.05
Deploy on Servor button
Maintain Docker (macOS) 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.06
More containers recipes
- 01Docker EngineDocker Engine + Compose from the official repository, service active, hello-world verified.
- 02Docker ComposeDocker Compose plugin (docker compose), installed and verified.
- 03PodmanPodman (daemonless containers, rootless capable), verified.
- 04PortainerPortainer CE (LTS) Docker management web UI, admin preconfigured.
- 05k3s (lightweight Kubernetes)Single-node k3s cluster. Destructive: configures networking and a container runtime.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.