Chapter 2. Running Red Hat Quay in debug mode
Red Hat recommends gathering your debugging information when opening a support case. Running Red Hat Quay in debug mode provides verbose logging to help administrators find more information about various issues. Enabling debug mode can speed up the process to reproduce errors and validate a solution for things like geo-replication deployments, Operator deployments, standalone Red Hat Quay deployments, object storage issues, and so on. Additionally, it helps the Red Hat Support to perform a root cause analysis.
2.1. Running a standalone Red Hat Quay deployment in debug mode
Running Red Hat Quay in debug mode provides verbose logging to help administrators find more information about various issues. Enabling debug mode can speed up the process to reproduce errors and validate a solution.
Use the following procedure to run a standalone deployment of Red Hat Quay in debug mode.
Procedure
Enter the following command to run your standalone Red Hat Quay deployment in debug mode:
$ podman run -p 443:8443 -p 80:8080 -e DEBUGLOG=true -v /config:/conf/stack -v /storage:/datastorage -d {productrepo}/{quayimage}:{productminv}
To view the debug logs, enter the following command:
$ podman logs quay
2.2. Running the Red Hat Quay Operator in debug mode
Use the following procedure to run the Red Hat Quay Operator in debug mode.
Procedure
Enter the following command to edit the
QuayRegistry
custom resource definition:$ oc edit quayregistry <quay_registry_name> -n <quay_namespace>
Update the
QuayRegistry
to add the following parameters:spec: - kind: quay managed: true overrides: env: - name: DEBUGLOG value: "true"
-
After the Red Hat Quay Operator has restarted with debugging enabled, try pulling an image from the registry. If it is still slow, dump all dogs from all
Quay
pods to a file, and check the files for more information.