Docker Socket Proxy

Allows you to control which features of docker to be exposed and available to others.

So that you do not have to expose the docker socket directly (that is equivalent to giving the user root access).

Based on https://github.com/Tecnativa/docker-socket-proxy

Changes compared to Tecnativa/docker-socket-proxy

Noticable changes:

• Simplified implementation to only two files
• Upgraded HAProxy to 3.2 LTS
• Fixed warnings
• Proxy config changes:
  • Allow POSTs to start/stop/restart depending on corresponding setting, without the need to enable the POST setting
  • Removed unlimited timeout on events paths
    • Unlimited timeout may be needed in some cases/tools: Tecnativa/docker-socket-proxy#98
  • Removed option redispatch (didn't do anything as it's only a single backend server)
  • Set retries 0 instead of 3

Example usage

Docker compose usage example:

services:
  docker-proxy:
    build: https://github.com/Qtax/docker-socket-proxy.git
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - DISABLE_IPV6=1
      - CONTAINERS=1
      - INFO=1
    cap_drop:
      - ALL
    security_opt:
      - no-new-privileges=true

Then other containers (on the same network) can use it by setting (or equivalent):

DOCKER_HOST=tcp://docker-proxy:2375

To update and rebuild you can run: docker compose build --pull