Stopping Containers
When you’re done testing the workflow, you can bring down the containers by type Ctrl + c in the terminal that runs the docker compose command. Or, in another terminal that’s located in the folder path containing the file docker-compose.yaml, you can use the command below to shutdown the workflow:
docker compose down
Please note that this operation will only shutdown the containers, but won’t delete them. You can still see them by listing all existing containers in the Docker repository by running:
docker ps -a
Example output:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dfe095dcaec4 nvcr.io/nim/mit/diffdock:1.2.0 "/opt/nvidia/nvidia_…" 2 hours ago Exited (0) 8 seconds ago cadd-diffdock
ca78e5e08e82 nvcr.io/nvstaging/nim/alphafold2:1.0.0 "/opt/nvidia/nvidia_…" 2 hours ago Exited (0) 2 seconds ago cadd-alphafold2
2e61f80ca280 nvcr.io/nim/nvidia/molmim:1.0.0 "/opt/nvidia/nvidia_…" 2 hours ago Exited (0) 6 seconds ago cadd-molmim
You can still use the docker compose up command to re-start these containers. And, you can use the following commands to permanently remove these containers:
docker rm cadd-alphafold2 cadd-molmim cadd-diffdock
The data and model cache will be kept in the cache folder on the host, so it won’t need to download them when re-launch the workflow.