You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✔ DRY-RUN MODE - Container nginx-golang-mysql-backend-1 Started 0.0s
193
193
✔ DRY-RUN MODE - Container nginx-golang-mysql-proxy-1 Started Started
194
194
```
195
-
You could see that the first step will be to pull the image defined by `db` service, then build the `backend` service.
196
-
After that, containers will be created, the `db` service started and the `backend` and `proxy` will wait until `db` service is healthy to start.
195
+
From the example above, you can see that the first step is to pull the image defined by `db` service, then build the `backend` service.
196
+
Next, the containers are created. The `db` service is started, and the `backend` and `proxy` wait until the `db` service is healthy before starting.
197
197
198
-
The Dry Run mode is not supported by all commands, especially by the command which doesn't change the state of a Compose stack
198
+
Dry Run mode does not currently work with all commands. In particular, you cannot use Dry Run mode with a command that doesn't change the state of a Compose stack
199
199
such as `ps`, `ls`, `logs` for example.
200
200
201
201
Here the list of commands supporting `--dry-run` flag:
0 commit comments