Closed rogerscuall closed 6 years ago
I haven't faced the same issue nor heard of a similar from other readers. Is there a proxy or VPN that might cause such a delay?
Nope, there is no VPN or proxy involved.
I added .env
file with COMPOSE_HTTP_TIMEOUT=300
to the vfarcic/books-ms
repo. That should add that env. var. to all compose commands. Can you pull the latest code from the repo and give it a try?
Assuming that the issue is closed. Please reopen it if you're still experiencing the problem.
Sorry I forgot to reply. That worked perfectly.
On Sat, Dec 16, 2017 at 6:41 PM Viktor Farcic notifications@github.com wrote:
Assuming that the issue is closed. Please reopen it if you're still experiencing the problem.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/vfarcic/ms-lifecycle/issues/30#issuecomment-352219918, or mute the thread https://github.com/notifications/unsubscribe-auth/AFfdjxM-dWoKPB7cmIOM2kBwaEBtG5PWks5tBFUqgaJpZM4QYI6a .
I have noticed that in the pre-deployment test and post-deployment test the is a play that uses docker-compose and I'm getting almost always a timeout, just following the exactly the error and increasing the
COMPOSE_HTTP_TIMEOUT
to 300 fixes the problem and permits the playbook from stopping with errors.