From 778d436c416ec47ea3a70904af9abf55d298f733 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Tue, 17 Oct 2017 16:54:45 +0800 Subject: [PATCH] Update startup-order.md --- compose/startup-order.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compose/startup-order.md b/compose/startup-order.md index 2b2744fd08..1dcf044457 100644 --- a/compose/startup-order.md +++ b/compose/startup-order.md @@ -1,7 +1,7 @@ --- description: How to control service startup order in Docker Compose keywords: documentation, docs, docker, compose, startup, order -title: Controlling startup order in Compose +title: Control startup order in Compose notoc: true --- @@ -29,7 +29,7 @@ need this level of resilience, you can work around the problem with a wrapper script: - Use a tool such as [wait-for-it](https://github.com/vishnubob/wait-for-it), - [dockerize](https://github.com/jwilder/dockerize) or sh-compatible + [dockerize](https://github.com/jwilder/dockerize), or sh-compatible [wait-for](https://github.com/Eficode/wait-for). These are small wrapper scripts which you can include in your application's image and will poll a given host and port until it's accepting TCP connections.