Chapter 2. Running Red Hat Quay in debug mode

Procedure

1. 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}

2. To view the debug logs, enter the following command:

   $ podman logs <quay_container_name>

Procedure

1. Enter the following command to run your LDAP Red Hat Quay deployment in debug mode:

   $ podman run -p 443:8443 -p 80:8080 -e DEBUGLOG=true -e USERS_DEBUG=1  -v /config:/conf/stack -v /storage:/datastorage -d {productrepo}/{quayimage}:{productminv}

2. To view the debug logs, enter the following command:

   $ podman logs <quay_container_name>

   Important

   Setting USERS_DEBUG=1 exposes credentials in clear text. This variable should be removed from the Red Hat Quay deployment after debugging. The log file that is generated with this environment variable should be scrutinized, and passwords should be removed before sending to other users. Use with caution.

Procedure

1. Enter the following command to edit the QuayRegistry custom resource definition:

   $ oc edit quayregistry <quay_registry_name> -n <quay_namespace>

2. Update the QuayRegistry to add the following parameters:

   spec:
     - kind: quay
       managed: true
       overrides:
         env:
         - name: DEBUGLOG
           value: "true"

3. 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 logs from all Quay pods to a file, and check the files for more information.