> However, you might see docker-proxy eating a lot of CPU due to increased traffic. You can say that again. Tried running Docker container with large range of

> However, you might see docker-proxy eating a lot of CPU due to increased traffic. You can say that again. Tried running Docker container with large range of exposed ports once (because SIP)... Each port got its own docker-proxy and the system basically suffocated. Not a nice view. :)