Is your feature request related to a problem? Please describe.
I am using socket-proxy with the per-container labels for permissions. It's not always clear which permissions are needed by a Docker client. I now use debug logging and allow all to see what calls a certain client is using and create regexes for those accordingly.
Describe the solution you'd like
Either a general 'logging only' option for socket-proxy or a per container label, that would allow me to log warnings for each request that doesn't pass the current rules, but still allow it so it doesn't stop my client containers from working.
Describe alternatives you've considered
Some months ago I suggested this as well and @amanda-wee came with the option of enabling debug logs and scanning them. I now have a second instance of socket-proxy deployed with debug logging and assign only one or two clients to that, but there can still be quite some logs sometimes.
Is your feature request related to a problem? Please describe.
I am using socket-proxy with the per-container labels for permissions. It's not always clear which permissions are needed by a Docker client. I now use debug logging and allow all to see what calls a certain client is using and create regexes for those accordingly.
Describe the solution you'd like
Either a general 'logging only' option for socket-proxy or a per container label, that would allow me to log warnings for each request that doesn't pass the current rules, but still allow it so it doesn't stop my client containers from working.
Describe alternatives you've considered
Some months ago I suggested this as well and @amanda-wee came with the option of enabling debug logs and scanning them. I now have a second instance of socket-proxy deployed with debug logging and assign only one or two clients to that, but there can still be quite some logs sometimes.