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. 01recondistro, version, codename and package manager (apt or dnf)
2. 02reconDocker already installed? daemon version
3. 03recondaemon active?
4. 04reconconflicting packages (distro docker.io, podman-docker, containerd, runc)
5. 05reconofficial Docker repository already configured?
6. 06reconexisting routes overlapping Docker default networks (172.17-31.x, 192.168.x) — may cut access
7. 07reconexisting daemon.json (to preserve)
8. 08reconfree disk space for /var/lib/docker (>= 10 GB recommended)
9. 09actAdd the official Docker repositoryverify
10. 10actInstall Docker Engine + Composeverify
11. 11actNon-overlapping Docker networks (only if recon found a conflict)verify
12. 12actEnable the daemonverify
13. 13actVerify with hello-worldverify
14. 14actAdd the user to the docker group (only if a user 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. 01verifyAdd the official Docker repositoryVerified byapt-get update -qq && apt-cache policy docker-ce | grep -c download.docker.com || dnf repolist 2>/dev/null | grep -ci docker
2. 02verifyInstall Docker Engine + ComposeVerified bydocker --version && docker compose version
3. 03verifyNon-overlapping Docker networks (only if recon found a conflict)Verified bydockerd --validate --config-file /etc/docker/daemon.json
4. 04verifyEnable the daemonVerified bysystemctl is-active docker
5. 05verifyVerify with hello-worldVerified bydocker run --rm hello-world 2>&1 | grep -c 'Hello from Docker'
6. 06verifyAdd the user to the docker group (only if a user is provided)Verified byid -nG ${user} | grep -cw docker

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 Engine 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 ComposeDocker Compose plugin (docker compose), installed and verified.
2. 02PodmanPodman (daemonless containers, rootless capable), verified.
3. 03PortainerPortainer CE (LTS) Docker management web UI, admin preconfigured.
4. 04k3s (lightweight Kubernetes)Single-node k3s cluster. Destructive: configures networking and a container runtime.
5. 05WatchtowerAutomatic, scheduled updates for Docker containers.