Add HTTP debug logging for Docker API calls#533
Conversation
|
@athongsamai @awmirantis @smerkviladze could you take a look at this or assign some reviewers that could? thanks! |
|
@chenyaooo i saw you recently dropped an update for this repo, could you 👀 this PR or ping someone who's able to? thanks! |
|
@athongsamai @awmirantis @smerkviladze @chenyaooo any of you there? |
|
@cnuss thanks for opening this PR. |
|
@athongsamai done! sorry i thought i had that turned on |
athongsamai
left a comment
There was a problem hiding this comment.
LGTM, thanks for good PR!
|
thanks @athongsamai ❤️ !! can you ping a 2nd reviewer to 👀 for me? i might have a couple more PRs coming up as i'm trying to get a |
Summary
This PR adds comprehensive HTTP debug logging for Docker API calls to aid in troubleshooting and debugging issues with the Docker client integration.
Changes
wrappedTransport) that intercepts Docker API requests and responsesgetDockerClient: Updated to automatically apply the debug transport when log level is set to debug or higher--log-levelflag description to list all available log levels (panic, fatal, error, warn, info, debug, trace) and indicate that 'debug' and 'trace' levels enable Docker API loggingExample Output
Info Level (default)
Debug Level
Trace Level
Files Changed
cmd/server.go: Updated--log-levelflag help text to document available levels and Docker API logging behaviorlibdocker/client.go: Modified to conditionally apply debug transport based on log levellibdocker/debug.go: New file implementing the HTTP debug transport wrapperlibdocker/debug_test.go: Comprehensive tests for debug transport functionalitylibdocker/client_test.go: Tests forgetDockerClientwith debug transport integrationBenefits
Fixes #532
🤖 Generated with Claude Code