Socket Proxy
A lightweight, secure-by-default Unix socket proxy that safely mediates access to a restricted socket, originally created to expose the Docker socket to…
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.
71/100 Good
- Maintained
- 100last commit 28 days ago
- Popular
- 53468 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 468
- Open issues
- 16
- Last commit
- 2026-10-24
- Latest release
- 1.13.2
- Activity
- steady
Checked 23 days ago - source: GitHub (wollomatic/socket-proxy)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Run it with the Docker socket mounted Use the provided `docker run` command; it mounts /var/run/docker.sock (the file Docker uses to accept control requests) and publishes port 2375 only on 127.0.0.1. Without the socket mount, the proxy has no way to talk to Docker, and without the 127.0.0.1 part, port 2375 can be reachable from your network. source
- Keep port 2375 private Bind port 2375 to 127.0.0.1 or a specific internal IP instead of just -p 2375:2375, because 2375 is the port that lets programs control Docker. Exposing it to all network interfaces can let anyone on the network control your containers. source
- Allow only the operations you need If another container must start or stop containers, add -e CONTAINERS=1 -e ALLOW_START=1 -e ALLOW_STOP=1 -e POST=1 when starting the proxy. Without the right flags, start/stop requests can be denied. source
- Traefik version compatibility For Traefik 2.11.31+ or 3.6.1+, add -allowHEAD=/_ping to the Socket Proxy command; otherwise Traefik falls back to Docker API v1.51 which breaks the provider on older Docker versions. source
Fetched yesterday - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need to mount the Docker socket for the proxy to work?
Yes. Run the proxy with /var/run/docker.sock mounted so it can talk to Docker. Without that mount, it has no way to communicate with Docker.
Should I expose port 2375 to the network?
No. Bind 2375 to 127.0.0.1 or a specific internal IP instead of publishing it on all interfaces. Exposing it can let anyone on the network control your Docker containers.
How do I allow another container to start or stop containers through the proxy?
Add the flags CONTAINERS=1, ALLOW_START=1, ALLOW_STOP=1, and POST=1 when starting the proxy. Without the right flags, start/stop requests can be denied.
Answers sourced from github.com, github.com
Community
Collected 48 days ago - public community threads