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. 01reconCompose v2+ already there? (then verify and skip)
2. 02reconIs Docker installed (prerequisite)?
3. 03reconofficial Docker repository present (docker-compose-plugin package available)?
4. 04recondistro and architecture (for the manual install)
5. 05reconlegacy standalone docker-compose v1 (leave it in place, just report it)
6. 06actInstall the compose pluginverify
7. 07actManual plugin install (only if no package is available)verify
8. 08actValidate a test compose fileverify

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. 01verifyInstall the compose pluginVerified bydocker compose version
2. 02verifyManual plugin install (only if no package is available)Verified bydocker compose version
3. 03verifyValidate a test compose fileVerified bydocker compose -f /tmp/servor-compose-test.yaml config -q && echo ok

SEC.03

Guardrails

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

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.

SEC.05

Deploy on Servor button

Maintain Docker Compose 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

1. 01Docker EngineDocker Engine + Compose from the official repository, service active, hello-world 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.