You may be able to diagnose and resolve issues should a Docker deployment fail, or the Hybrid Data Pipeline instance not work as expected. To investigate issues, you may access logs in the following ways.

Option 1. As a first line of investigation, you can access stdout and stderr outputs using the Docker logs command. The following logs command will show stdout and stderr outputs:
docker logs container_name

Option 2. If deployment fails and a container is not created, the Hybrid Data Pipeline logs are bundled into a compressed archive file named d2c.timestamp.tar.gz and written to the shared file location. The deployment log files include: deployment.log, error.log, and final.log.

Option 3. If deployment succeeds but the server is not working as expected, you can access logs directly in the Docker container. To access the container, you must open a supported shell on the container. For example:

docker exec -it container_name bash

After opening the shell, you may navigate to the Docker container directory. For example:

cd opt/Progress/DataDirect/Hybrid_Data_Pipeline/Hybrid_Server
Note: See Deployment logs for details about these and other relevant logs.