Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/mietzen/docker-redsocks-proxy
Docker Redsocks Proxy Image with Example
https://github.com/mietzen/docker-redsocks-proxy
docker proxy socks5 vpn
Last synced: 2 months ago
JSON representation
Docker Redsocks Proxy Image with Example
- Host: GitHub
- URL: https://github.com/mietzen/docker-redsocks-proxy
- Owner: mietzen
- License: mit
- Created: 2024-08-04T11:47:04.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2024-10-17T14:36:58.000Z (4 months ago)
- Last Synced: 2024-10-19T21:09:18.383Z (4 months ago)
- Topics: docker, proxy, socks5, vpn
- Language: Shell
- Homepage:
- Size: 52.7 KB
- Stars: 5
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Docker Redsocks Proxy
With this container you can redirect all http and https traffic through a socks5 proxy.
## Examples:
In this example the http and https traffic of the debian container will always be redirected through the set proxy. This perquisites that your docker host is already running inside the VPN Network (In this example Mullvad VPN).
```yaml
services:
redsocks:
image: mietzen/redsocks-proxy:stable
hostname: redsocks
cap_add:
- NET_ADMIN
- NET_RAW
environment:
- PROXY_SERVER=de-ber-wg-socks5-005.relays.mullvad.net
- PROXY_PORT=1080
dns: 9.9.9.9 # Optional
restart: unless-stopped
debian:
image: mietzen/debian-curl-jq:stable
depends_on:
- redsocks
network_mode: service:redsocks
command: /bin/bash -c "while true; do curl -sSL https://am.i.mullvad.net/connected && sleep 10; done"
restart: unless-stopped
```
```shell
Attaching to debian-1, redsocks-1
redsocks-1 | Configuration:
redsocks-1 | PROXY_SERVER: de-ber-wg-socks5-005.relays.mullvad.net
redsocks-1 | PROXY_PORT: 1080
redsocks-1 | Setting config variables
redsocks-1 | Restarting redsocks and redirecting traffic via iptables
redsocks-1 | Restarting redsocks: redsocks.
redsocks-1 | IP Address: 193.32.248.181
redsocks-1 | 1722762436.099561 notice main.c:165 main(...) redsocks started, conn_max=131072
redsocks-1 | 1722762436.183053 info redsocks.c:1243 redsocks_accept_client(...) [172.19.0.2:38986->45.83.223.233:443]: accepted
redsocks-1 | 1722762436.240962 info redsocks.c:1243 redsocks_accept_client(...) [172.19.0.2:39002->45.83.223.233:443]: accepted
debian-1 | You are connected to Mullvad (server de-ber-wg-socks5-005). Your IP address is 193.32.248.181
```
### Published ports
If your container behind redsocks exposes a port the port is mirrored to the redsocks containers, to access just open the port on the redsocks container:
```yaml
services:
redsocks:
image: mietzen/redsocks-proxy:stable
hostname: redsocks
ports:
- "8080:2001"
cap_add:
- NET_ADMIN
- NET_RAW
environment:
- PROXY_SERVER=de-ber-wg-socks5-005.relays.mullvad.net
- PROXY_PORT=1080
dns: 9.9.9.9
restart: unless-stopped
whoami:
image: traefik/whoami
depends_on:
- redsocks
command:
- --port=2001
network_mode: service:redsocks
restart: unless-stopped
```
```shell
$ curl http://localhost:8080/
Hostname: redsocks
IP: 127.0.0.1
IP: ::1
IP: 172.20.0.2
IP: fe80::42:acff:fe14:2
RemoteAddr: 172.16.0.1:59666
GET / HTTP/1.1
Host: localhost:8080
User-Agent: curl/8.9.1
Accept: */*
```
### Stacked service network
If your docker host is not already connected to the mullvad VPN you might want to use [gluetun](https://hub.docker.com/r/qmcgaw/gluetun) and stack the network connection, e.g.:
```yaml
# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# !!! NOT A WORKING EXAMPLE !!!
# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# You need to setup gluetun yourself!
services:
gluetun:
image: qmcgaw/gluetun
hostname: gluetun
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- ./gluetun:/gluetun
environment:
# See https://github.com/qdm12/gluetun-wiki/tree/main/setup#setup
# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# !!! HERE IS STILL SOME SETUP NEEDED!!!
# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# ...
restart: unless-stopped
dns: 9.9.9.9
redsocks:
image: mietzen/redsocks-proxy:stable
hostname: redsocks
depends_on:
- gluetun
cap_add:
- NET_ADMIN
- NET_RAW
environment:
- PROXY_SERVER=de-ber-wg-socks5-005.relays.mullvad.net
- PROXY_PORT=1080
network_mode: service:gluetun
restart: unless-stopped
debian:
image: mietzen/debian-curl-jq:stable
depends_on:
- redsocks
network_mode: service:redsocks
command: /bin/bash -c "while true; do curl -sSL https://am.i.mullvad.net/connected && sleep 10; done"
restart: unless-stopped
```
**Sources:**
- [PXke's blog: Using redsocks to proxy a docker container traffic](https://web.archive.org/web/20240302223218/https://blog.pxke.me/redsocksdocker.html)
- [SO-Answer from marlar: How to make docker container connect everything through proxy](https://stackoverflow.com/a/71099635)
- [Docker Community Forums: Diffcult to find documentation about how network_mode: “service:” works](https://web.archive.org/web/20240721062403/https://forums.docker.com/t/diffcult-to-find-documentation-about-how-network-mode-service-service-name-works/137008)