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 present? binary path (for ExecStart)
- 02recona scheduled prune already exists (timer or cron)? do not duplicate it
- 03reconcurrently reclaimable space
- 04actCreate the cleanup serviceverify
- 05actCreate the weekly timerverify
- 06actEnable the scheduleverify
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.
- 01verifyCreate the cleanup serviceVerified by
systemd-analyze verify /etc/systemd/system/docker-prune.service && echo ok - 02verifyCreate the weekly timerVerified by
systemd-analyze verify /etc/systemd/system/docker-prune.timer && echo ok - 03verifyEnable the scheduleVerified by
systemctl is-active docker-prune.timer
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never add --volumes to the automatic prune (data destruction). Do not run an immediate prune without asking. If a scheduled prune already exists, report it instead of creating a second one. Running containers and their images are never touched.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${retention_hours} | Keep anything younger than (hours) |
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.
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.06
Deploy on Servor button
Maintain Docker cleanup (cron) 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.
Dark background
Light background[](https://servor.app/deploy/setup-docker-prune)SEC.07
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.