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 and active (prerequisite)
- 02reconregistry already deployed? existing registry_data volume (to reuse)?
- 03reconport 5000 free?
- 04reconcredentials already generated?
- 05reconreverse proxy present (Caddy or Nginx) for TLS if a domain is provided
- 06actGenerate the passwordverify
- 07actCreate the htpasswd file (bcrypt)verify
- 08actRun the registryverify
- 09actTLS reverse proxy (only if a domain 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.
- 01verifyGenerate the passwordVerified by
stat -c %a /opt/registry/admin_password - 02verifyCreate the htpasswd file (bcrypt)Verified by
grep -c '^${username}:\$2y\$' /opt/registry/auth/htpasswd - 03verifyRun the registryVerified by
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:5000/v2/; echo; curl -s -o /dev/null -w '%{http_code}' -u ${username}:$(cat /opt/registry/admin_password) http://127.0.0.1:5000/v2/ - 04verifyTLS reverse proxy (only if a domain is provided)Verified by
curl -s -o /dev/null -w '%{http_code}' -u ${username}:$(cat /opt/registry/admin_password) https://${domain}/v2/
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
If Docker or the compose plugin is missing: stop and tell the user to run the "Docker Engine" recipe first (do not install it on the fly). Never expose a registry without TLS + auth: it listens on 127.0.0.1:5000, remote access goes through the TLS reverse proxy. Never delete the registry_data volume. Say where to read the password: /opt/registry/admin_password. Do not log the password.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${username} | Registry user |
| ${domain} | Domain (optional, for TLS) |
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 Private Docker registry 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/install-registry)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.