Use case
Deploy one Compose file to every Raspberry Pi you own
Stop SSH-ing into each Pi to pull and restart. Register the devices, create a release, and roll it out with a health gate.
For: Developers and makers with a handful of Pis at home or at customer sites.
deploy-docker-01Raspberry Pi 5 · arm64
Healthy- Desired
- collector 1.8.4
- Actual
- collector 1.8.4
- Docker
- 29.0.2
- CPU
- 12%
- RAM
- 43%
- Disk
- 31%
- Temp
- 48 °C
- Uptime
- 38 d
- Last deploy
- 2 d ago
collector1.8.4healthy
mqtt2.0.22healthy
watchdog2.1.0healthy
LogsDiagnosticsRestart appDeployRoll back
The usual pain
- Every device is slightly different because it was updated by hand at a different time.
- A pull that fails on one Pi goes unnoticed until something breaks.
- The .env file lives in a chat message somewhere.
With Simple Docker Ops
- One release, pinned to image digests, applied identically everywhere.
- Per-device deployment status, container health, and logs in one place.
- Secrets scoped to the fleet and delivered only to the agent.
Setup
- 1Run the install command on each Pi and pair it with the code it prints.
- 2Paste your docker-compose.yml as an application and cut a release.
- 3Deploy to the fleet; watch each device report healthy.
Questions
Does it work with the Compose file I already have?
Yes. Compose v2 files are accepted as-is. Variables become release configuration; secrets are separated out.
Add your first device free.
Five devices and five gigabytes of registry on the Free plan. No card, no sales call, no Kubernetes.
curl -fsSL https://simpledockerops.com/install | sudo sh