dockersocket
This is a security-enhanced proxy for the Docker Socket.
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.
60/100 Good
- Maintained
- 75last commit 5 days ago
- Popular
- 692,909 GitHub stars
- Easy to install
- 201 install platform, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 2,909
- Open issues
- 56
- Last commit
- 2026-11-17
- Latest release
- v0.6.0
- License
- Apache-2.0
- Activity
- rising
Checked today - source: GitHub (Tecnativa/docker-socket-proxy)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked today - source: Docker Hub image tags and published docs
First-install notes
No first-install notes yet.
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need to run the proxy with special flags or mounts?
Yes, use --privileged and mount /var/run/docker.sock into the container because the Docker socket connection is privileged in some SELinux/AppArmor contexts.
Should the proxy's published port be reachable from the public internet?
No, the documentation says never expose the container's port to a public network. Keep it only on Docker networks where the proxy and the service that uses it reside.
How do I block or allow specific Docker API sections?
Set the API-section environment variables to 0 to revoke access or 1 to grant access. The variables normally match URL prefixes such as AUTH for the /auth/* parts of the API.
Does the proxy add TLS for Docker API traffic?
No, the image does not include TLS support and provides a plain HTTP proxy to the host Docker Unix socket. You are expected to restrict access through Docker's built-in firewall.
How do I make my local Docker CLI use the proxy?
Run the proxy with the host port bound to 127.0.0.1:2375 and set DOCKER_HOST so the Docker client uses localhost on port 2375.
Answers sourced from github.com
Community
No community discussions collected yet.
