Troubleshooting in a Docker Container environment

This section describes how to troubleshoot in your Docker container environment.

When you encounter an issue in your containerized environment, run the following checks to assist you with troubleshooting process.

Generic Checks

Get container information such as, container-id and check the node status if it is Up
```
docker ps -a
```
Retrieve the logs for a container
```
docker logs <container-id>
```

When a container deployment fails investigate the cause and follow the procedure given below over command line:

Use the command below to stop the failed container, if it is still running
```
docker stop <container-id>
```

Check the container logs using the command
```
docker logs <container-name>
```
From the mapped path on Storage Volume, check the silent installation logs cdaiLog.txt inside the work directory.
IBM Connect:Direct for UNIX traces for PMGR, SMGR or CMGR can be enabled using the Connect:Direct Web Services. From the mapped path on Storage Volume, check the traces generated inside the work directory.
IBM Connect:Direct for UNIX statistics can be checked in the work directory inside the mapped path on Storage Volume.