wowu/docker-rollout

🚀 Zero Downtime Deployment for Docker Compose

View on GitHub ↗Jump to charts ↓Open shareable report →

wowu/docker-rollout has 3k+ stars and 100+ forks on GitHub, is written in Shell, and was last pushed on Oct 8, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 20th, 2026
Created on February 6th, 2023
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 106
Total Stargazers: 3,354 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 40.4 hours
Mean response time: 15.9 days
90th percentile: 24.7 days
Tracked items: 23

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 393 days
Stale 30+ days: 4
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

docker-rollout is a Docker CLI plugin that enables zero downtime deployment for Docker Compose services.

The tool solves the problem of service interruption during deployments by implementing a rolling update strategy. When you run docker rollout on a service, it scales the service to twice its current number of instances, waits for the new containers to become healthy using Docker healthchecks, and then removes the old containers. This approach keeps traffic flowing to healthy instances throughout the update process.

Teams should adopt this tool if they run services on Docker Compose and need to deploy updates without downtime. It works best for applications already using a reverse proxy like Traefik or nginx-proxy to route traffic, since the tool cannot manage port bindings directly. The plugin integrates seamlessly into existing deployment scripts as a drop-in replacement for docker compose up. However, there are constraints: services cannot define container_name or ports in the compose file, and to avoid dropping in-flight requests, you need to implement container draining with a pre-stop hook that marks old containers as unhealthy before removal.

Development activity shows consistent maintenance with regular updates addressing user feedback and edge cases. The project maintains clear documentation with examples and detailed option descriptions. The codebase remains focused on its core functionality without scope creep, and the tool has been refined based on practical deployment scenarios including the addition of container draining support.