It provides a way (as multiplatform as Docker is) to connect to a HTTP PROXY standard protocol to get to a SOCKS5 server with advanced route configuration, which is not readly provided by all softwares for free, like in Windows, which you can configure a simples HTTP proxy locally (see configuration at bottom).
It can also be use in this case, for many applications, like some java implementations that can connect to SOCKS but are not enabled to correctly pass the user and password to authenticate SOCKS connection, so it can act as a SOCKS without authentiction chaining to an authenticated SOCKS.
References: tsocks ncat microsocks
Adjust the tsocks.conf replacing the variables by your user name and password, and other configurations related to your SOCKS5 paths:
default_user = user
default_pass = password
and check if the tsocks.conf is pointing to the correct path inside docker-compose.yml and run by using :
docker-compose up
docker run -v path/tsocks.conf:/etc/tsocks.conf -p 3128:3128 -p 1080:1080 greogoriomomm/multsocks:latest
Example:
export JVM_ARGS='-Dhttp.proxyHost=localhost -Dhttp.proxyPort=3128 -Dhttp.nonProxyHosts="localhost|127.0.0.1|host.example.com"'
export JVM_ARGS='-DsocksProxyHost=localhost -DsocksProxyPort=1080'
Unix:
export http_proxy="http://127.0.0.1:3128"
export https_proxy="http://127.0.0.1:3128"
export no_proxy="127.0.0.1,localhost"
curl http://host.target.domain
Or configure the Windows Proxy :

Content type
Image
Digest
Size
4 MB
Last updated
about 6 years ago
docker pull gregoriomomm/multsocks