Issues
- 4
True zero-downtime deployment by request draining
#21 opened by wowu - 0
Watchtower Intergration
#35 opened by PsycloneTM - 6
Old instance 50% of the time
#32 opened by bartoszkrawczyk2 - 0
Notice: Blog post
#34 opened by jwillmer - 3
Uses the older image for the new container
#31 opened by dcodesdev - 4
- 4
- 1
unknown flag: --quiet error
#29 opened by kerimembel - 1
Performance problem
#26 opened by afasciaux - 4
Remanining containers after rollout
#25 opened by rap2hpoutre - 8
- 2
remove SC2086 check as it is not very helpful and should be human decided (as you noticed)
#24 opened by Morriz - 3
zero downtime is a promise not held in reality: can you add a hook (so we can reload the proxy)?
#23 opened by Morriz - 1
- 6
Support `docker --context`
#13 opened by tadamcz - 5
Error after deploiement finish : 20#20: *23 connect() failed (111: Connection refused) while connecting to upstream
#14 opened by hadpro24 - 1
How can we rollout the proxy service itself?
#12 opened by oseau - 4
Number of container don't match expected number
#10 opened by Belphemur - 4
I'd like to request a minimal example demonstrating how to perform zero-downtime deployment using docker rollout with Nginx and Rails.
#9 opened by activeliang - 1
Compose project name not checked during scaling
#3 opened by usr3 - 2
Support profiles
#5 opened by fliespl - 4
How to deploy to remote instance
#6 opened by fliespl