One socket-proxy per container or one for all? #3
-
Hi, i am wondering whats the best way to use the socket proxy. I have two docker services running that require access to the socket-proxy. Currently i connect both to one socket-proxy that i run in a separete compose file. environment:
DOCKER_HOST: tcp://socket-proxy:2375
networks:
- socket-proxy-net
... Now i am wondering if its better to have one socket-proxy per compose.yml since it would allow me to take advantage of the health check and depends_on. How do you use it? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You can run multiple socket proxies if you need the health check feature. This is not overkill since the socket proxy is a very small process only consuming a few MB of memory. |
Beta Was this translation helpful? Give feedback.
You can run multiple socket proxies if you need the health check feature. This is not overkill since the socket proxy is a very small process only consuming a few MB of memory.