From d2974a5d3b2565b254ce975cd209f85db89665d1 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Sat, 1 Apr 2017 14:42:38 +0800 Subject: [PATCH] Update startup-order.md (#2591) --- 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 224e564c84..64d5bb1333 100644 --- a/compose/startup-order.md +++ b/compose/startup-order.md @@ -1,6 +1,6 @@ --- description: How to control service startup order in Docker Compose -keywords: documentation, docs, docker, compose, startup, order +keywords: documentation, docs, docker, compose, startup, order title: Controlling startup order in Compose notoc: true --- @@ -8,7 +8,7 @@ notoc: true You can control the order of service startup with the [depends_on](compose-file.md#depends-on) option. Compose always starts containers in dependency order, where dependencies are determined by -`depends_on`, `links`, `volumes_from` and `network_mode: "service:..."`. +`depends_on`, `links`, `volumes_from`, and `network_mode: "service:..."`. However, Compose will not wait until a container is "ready" (whatever that means for your particular application) - only until it's running. There's a good