In the case of OpenDCRE failures or errors, it is helpful to know how some basic debugging steps.
As covered in the subsequent sections here, OpenDCRE logs out to files within the container. One exception to this is for errors on container startup. In addition to logging out to file, it logs out to stderr of the container (pid 1), so it is accessible via docker logs. If a startup error should occur, the OpenDCRE container should terminate. In this case, it is often prudent to check the docker logs first to see if there is any information pertaining to a startup error.
A startup error likely will only happen if there is a serious misconfiguration, or if building a custom OpenDCRE image, something was changed to break the initialization process.
With debug logging enabled, there will be two sets of logs captured – the error logs (same as the production logs), and the debug logs.
There are two primary methods for accessing a container's logs: docker exec and docker cp.
This will drop you into the working directory of the container, /opendcre. From there, navigate to /logs, where all of the container logs are kept.
Using docker cp can be done when the container is running or when it has terminated. It is used to copy the logs from the container file system to the host file system.
This will place the log files on the host system at the specified location.
© Copyright 2017, Vapor IO. Revision 927334b0.