Well, the trick is that I have downtime but it last for only a few seconds. Docker pull <image name> Docker container stop <container name> Docker run <o

Well, the trick is that I have downtime but it last for only a few seconds. Docker pull <image name> Docker container stop <container name> Docker run <opts> <image name> This does result in a “hiccup” for any clients wanting to connect. They will see a 502 gateway error at which point they should retry with exponential backoff. And that is the trick — make the client retry with the exponential backoff. Document it as the expected behavior when that event arises. And for our traffic patterns this is acceptable.