Use case
Canary deployments for Compose workloads on real devices
Deploy to two test devices, then 10 percent, then everyone. Each wave waits for health. A failure threshold pauses or rolls back.
For: Anyone who has broken 50 remote devices with one push.
docker-compose-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
- All-at-once updates turn a bad image into a bad day.
- Health means "the container is running", which is not the same as "the application works".
With Simple Docker Ops
- Waves with configurable percentages, parallelism, and minimum healthy time.
- Container healthchecks plus HTTP and TCP probes evaluated on the device.
- One-click rollback to the previous known-good release.
Setup
- 1Set the strategy on the deployment: waves, threshold, on-failure action.
- 2Watch devices move through applying, healthy, or failed.
- 3Roll back with one click if the gate trips.
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