Skip to content

Add a configuration for the S3 driver log level

João Pereira requested to merge enable-s3-logs into release/2.8-gitlab

Problem

It's not possible to set the S3 driver log level using a configuration setting/environment variable. This makes it harder to debug issues, like #38 (closed).

Solution

Expose the S3 driver log level as a configuration parameter. This was done upstream as well: https://github.com/docker/distribution/pull/3057. The change proposed here has some slight modifications to allow setting the value during tests with a custom environment variable as well.

How to Use

Configuration File

This configuration setting can be set in the configuration file:

# ...
storage:
  s3:
    # ...
    loglevel: <level>

Environment Variable

This configuration setting can be set using the REGISTRY_STORAGE_S3_LOGLEVEL environment variable.

Possible Values

The possible log levels are the lowercase version of the AWS Go SDK LogLevelType values (see the documentation for a description of each):

  • logoff
  • logdebug
  • logdebugwithsigning
  • logdebugwithhttpbody
  • logdebugwithrequestretries
  • logdebugwithrequesterrors
  • logdebugwitheventstreambody
Edited by João Pereira

Merge request reports