Allow enable more verbose debug for s3 #2043
Labels
Comments
This was referenced Nov 29, 2019
openshift-merge-robot
added a commit
to openshift/docker-distribution
that referenced
this issue
Feb 9, 2021
UPSTREAM: docker/distribution: 3057: allow for optional S3 debugging -- closes issue distribution#2043
bverschueren
pushed a commit
to bverschueren/docker-distribution
that referenced
this issue
Apr 26, 2021
recent S3 storage issues made it very useful to be able to enable S3 API debug logging; contributing those simple enhancements back to the project; closes issue distribution#2043 from 2016
dmage
pushed a commit
to openshift/docker-distribution
that referenced
this issue
Nov 24, 2022
recent S3 storage issues made it very useful to be able to enable S3 API debug logging; contributing those simple enhancements back to the project; closes issue distribution#2043 from 2016
|
Closing, addressed in #4076 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I was investigating the problem with #2033.
I had quite work to get the request/response done to the aws s3.
I used the mitmproxy. But it was a bit complicated to get that working due ssl certs.
The simplest solution and that gave me a better result was enabling the
LogDebugWithHTTPBodyon registry/storage/driver/s3-aws/s3.go:Is pretty easy to see how the requests/responses are being done once that log is enabled.
I think would be great have this log enabled when the distribution config has
log.level: debug. If this feature is approved I am interested in implementing this change.The text was updated successfully, but these errors were encountered: