Separate socket-proxy needed for each container ?

[xd003]

Hello, I’m setting up this project for the first time. I have multiple containers that need access to the Docker socket. My question is, do I need to run a separate instance of the socket-proxy for each container compose file, or will a single instance be sufficient for all of them?

[wollomatic]

Hi @xd003,

each application should ideally have its own configuration and permission set. That’s why the recommended approach is to run a dedicated instance of the socket-proxy for each application. The memory footprint is very small, so the overhead is negligible.

Technically, you can use a single instance for multiple setups (see #5), but I wouldn’t recommend it.

There’s also an open issue aiming to make it possible to configure different hosts individually in the future.