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)
- 02reconportainer container and portainer_data volume already present?
- 03reconport 9443 free?
- 04reconadmin password already generated?
- 05actGenerate the admin passwordverify
- 06actCreate the volumeverify
- 07actRun Portainerverify
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 admin passwordVerified by
stat -c %a /opt/portainer/admin_password - 02verifyCreate the volumeVerified by
docker volume inspect -f {{.Name}} portainer_data - 03verifyRun PortainerVerified by
curl -sk -o /dev/null -w '%{http_code}' https://127.0.0.1:9443/
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). The Docker socket grants root access: by default Portainer only listens on 127.0.0.1 (access via SSH tunnel or reverse proxy). On 0.0.0.0, warn that Docker-published ports bypass ufw. Never delete the portainer_data volume. Say where to read the password: /opt/portainer/admin_password (user admin).
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${listen} | UI listen address |
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 Portainer 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-portainer)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.
- 04k3s (lightweight Kubernetes)Single-node k3s cluster. Destructive: configures networking and a container runtime.
- 05WatchtowerAutomatic, scheduled updates for Docker containers.
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.