docker-rollout-action
github.com/mtizima/docker-rollout-action- Category
- Developer Tools
- Rank
- No. 1676Tools index
Previous survey · No. 1586 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Deployment & Operations
- Interfaces
- Host Plugin
- GitHub
- 16 stars
- Latest release
- v1.0.0
- Date
About
A GitHub Action that deploys Docker Compose services to your own server over SSH without downtime. It uploads compose and env files, pulls images, runs migrations and updates services with docker-rollout, starting the new container beside the old one and removing the old one only after the new one is healthy. A release that fails its healthcheck is rolled back automatically, so the old containers keep serving traffic.
At a glance
Docker Rollout Deploy updates Docker Compose services on a remote server over SSH. It is worth evaluating when a web service can run old and new containers together behind a reverse proxy.
Good fit
Teams already using GitHub Actions and managing a small Compose deployment with reliable health checks.
Consider something else when
Keep another release workflow when the service cannot run overlapping instances or a migration breaks the old version.
Start here
Use a disposable Compose stack with a known health check. Send harmless requests during a normal rollout and a forced health failure, then inspect which container serves traffic.
Cost and requirements
Requires GitHub Actions, SSH access, Docker Compose and a reverse proxy. The action takes SSH credentials and a known-hosts entry.
Limits to know
The project documents a rolling path for eligible services and regular Compose updates for services with fixed names or ports. A failed health check does not reverse database migrations.
Sources checked 2026-11-05. Source-based assessment.
Tags
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.