Is your feature request related to a problem? Please describe.
The current implementation of the per-container allowlist only works in network mode https://github.com/wollomatic/socket-proxy#setting-up-per-container-allowlists
I want to use it with a unix socket! https://github.com/wollomatic/socket-proxy#using-a-unix-socket-instead-of-a-tcp-listener
Describe the solution you'd like
I'd like to use docker labels to configure allowlists per container even in unix socket mode, in the way that Traefik or Crowdsec do. It'll allow to keep both the ease of configuration of docker labels and the increased security of not risking networking accidents.
Describe alternatives you've considered
Continue using networking mode or set up one socket-proxy per container.
Is your feature request related to a problem? Please describe.
The current implementation of the per-container allowlist only works in network mode https://github.com/wollomatic/socket-proxy#setting-up-per-container-allowlists
I want to use it with a unix socket! https://github.com/wollomatic/socket-proxy#using-a-unix-socket-instead-of-a-tcp-listener
Describe the solution you'd like
I'd like to use docker labels to configure allowlists per container even in unix socket mode, in the way that Traefik or Crowdsec do. It'll allow to keep both the ease of configuration of docker labels and the increased security of not risking networking accidents.
Describe alternatives you've considered
Continue using networking mode or set up one socket-proxy per container.