Deployments currently use docker compose up -d --pull always --force-recreate, which stops and recreates all containers simultaneously, causing 10-30 seconds of downtime per deploy. docker-rollout eliminates this by scaling up new containers alongside old ones, health-checking, then removing old containers — zero-downtime.
The original investigation (gist from ~4 months ago) identified removing container_name as a blocker. That's now resolved — PR #628 confirmed all application services have no container_name and no host ports:.
First deploy does NOT require manually stopping stacks. docker-rollout works with running containers — it scales up alongside them, waits for health, then removes old ones. No manual intervention needed.