Avoid Proxy Headaches in Docker with redsocks
Proxying with Docker
When using docker under a corporate proxy, it can be cumbersome to
have a working networking in all containers. You often end up being
blocked by specific network access which does not seem to be
properly forwarded to the proper proxy. For example when using
Classic way of doing
There is a documented way of using a proxy, by adding command-line switches to your docker deamon. However, it does not seem to work everytime and could require exporting additional settings to your in-container applications (in my experience though).
Why not using docker
Nicolas pointed me an image he created to help with the setup of a corporate proxy. It uses redsocks under the hood that listen to the docker socket and automatically add the glue to do the forwarding through the proxy.
Easy proxying in docker is just one command away ! (fill in the blank of your proxy ip and port)
docker run \ --restart=always \ --privileged=true \ --net=host \ -d ncarlier/redsocks \ $PROXY_IP $PROXY_PORT