Mainfrezzer WireGuard Client

WireGuard Bridge is a Docker container that routes your container network traffic through a WireGuard VPN, supporting dual-stack and IPv6-only server…

  • Network Services
  • Tools & Utilities
WireGuard Bridge is a Docker container that routes your container network traffic through a WireGuard VPN, supporting dual-stack and IPv6-only server configurations. It bundles Privoxy as an HTTP proxy and microsocks as a SOCKS5 proxy, letting you direct specific container traffic through your VPN without reconfiguring individual containers. Ideal for self-hosters who need fine-grained VPN routing for Docker workloads.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

48/100 Fair

Maintained
73last commit 44 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 29 days ago

GitHub stars
0
Open issues
0
Last commit
2026-10-08
Activity
stale

Checked 9 days ago - source: GitHub (Mainfrezzer/wireguard-bridge)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s), 1.5 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Docker Quick Start Deploy with --cap-add=NET_ADMIN and --sysctl net.ipv4.conf.all.src_valid_mark=1. Mount your WireGuard config directory to /etc/wireguard/. Map port 1080 (SOCKS5) and 8080 (Privoxy). Set LAN_NETWORK and optionally LAN_NETWORK6 to your container subnets as comma-separated CIDR ranges. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What Docker permissions and Linux setting are required when deploying the container?

Add the NET_ADMIN capability and set the sysctl net.ipv4.conf.all.src_valid_mark=1. The README uses both for Docker run and Compose.

Which host ports expose the built-in proxy services?

Map 1080/tcp for the microsocks SOCKS5 proxy and 8080/tcp for the Privoxy HTTP proxy. If HTTPPORT is changed, add a matching port mapping.

How do you specify the IPv4 and IPv6 networks the container should handle?

Set LAN_NETWORK for IPv4 and LAN_NETWORK6 for IPv6. Multiple networks can be listed with a comma as the divider.

How can you avoid forcing all container traffic through the WireGuard tunnel?

Set DISABLE_TUNNEL_MODE to any value to disable VPN tunnel enforcement. This is useful when containers only need specific VPN IPs while otherwise using the normal internet connection.

Can the container randomly select a WireGuard client file from the mounted config directory?

Use ENABLE_RANDOM to enable random mode, which picks a file from /etc/wireguard at random. The README shows the variable as an environment setting for that behavior.

How is the container health check customized?

Set HEALTH_URL_CHECK to a custom URL or IP that the health check should ping. This lets you define the endpoint used for the container's health check.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads