Skip to content

Commit 23f90ce

Browse files
authored
Correct "docker compose down" commands NO_JIRA
1 parent 2741a31 commit 23f90ce

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

README.md

+12-3
Original file line numberDiff line numberDiff line change
@@ -155,8 +155,16 @@ CHECK: To check that the install has completed and that all the services are run
155155
docker compose ps
156156
```
157157

158-
which should show the state of the services to all be `Up`. If any services have the state `Up (unhealthy)` or `Exit` then restart the stack (`docker compose down` then repeat
159-
the `docker compose ... up -d` command run earlier). If the issues persist then please contact CCDC Support.
158+
which should show the state of the services to all be `Up`. If any services have the state `Up (unhealthy)` or `Exit` then restart the stack.
159+
160+
```sh
161+
# Include all config files from the "docker compose ... up -d" run earlier
162+
docker compose -f docker-compose.yml -f ... down
163+
# Same command to bring up the stack as before
164+
docker compose -f docker-compose.yml -f ... up -d
165+
```
166+
167+
If the issues persist then please contact CCDC Support.
160168

161169
For more information see the [Docker volumes documentation](https://docs.docker.com/compose/compose-file/#volumes).
162170

@@ -251,7 +259,8 @@ The latest images can be pulled whilst the stack is running and changes will onl
251259
```sh
252260
docker compose pull
253261
254-
docker compose down
262+
#Include all files you included when bringing up the stack
263+
docker compose -f docker-compose.yml -f ... down
255264
#Use one of the following commands:
256265
257266
#Use this command if you have no in-house databases and don't want to use macromolecule hub

0 commit comments

Comments
 (0)