Use the Docker CLI to pull this image
Run socat command in alpine container
Weekly auto-trigger docker build for socat when new version is released.
The Docker for Mac native macOS application provides use of docker engine without the need for vagrant or other virtualized linux operating system. Docker for Mac does not provide the same docker daemon configuration options as other versions of docker-engine. macOS-socat uses socat to establish a tcp socket bound to localhost which makes available the Docker for Mac API.
To publish the unix-socket (/var/run/docker.sock) to the Docker daemon as port 2376 on the local host (127.0.0.1):
$ docker pull alpine/socat $ docker run -d --restart=always \ -p 127.0.0.1:2376:2375 \ -v /var/run/docker.sock:/var/run/docker.sock \ alpine/socat \ tcp-listen:2375,fork,reuseaddr unix-connect:/var/run/docker.sock
WARNING: The Docker API is insecure by default. Please remember to bind the TCP socket to the
localhost interface otherwise the Docker API will be bound to all interfaces.
Docker does not allow easy publishing of ports on existing containers. Changing published ports is done by destroying existing containers and creating them with changed options. Alternative solutions require firewall access, and are vulnerable to changes in the addresses of said containers between restarts.
This image can be used to work-around these limitations by forwarding ports and linking containers
To publish port 1234 on container example-container as port 4321 on the docker host:
$ docker pull alpine/socat $ docker run \ --publish 4321:1234 \ --link example-container:target \ alpine/socat \ tcp-listen:1234,fork,reuseaddr tcp-connect:target:1234
Socat docker image by defintion does not use any EXPOSE inside Dockerfile. This may prejudice other containers that rely on this information, like nginx-proxy (https://github.com/nginx-proxy/nginx-proxy).
Using expose will allow nginx-proxy to properly detect and communicate with socat instance without opening the port on host like ports option does.
In the following example, socat will be used to relay a host Cockpit instance to the nginx-proxy image, allowing to rely on proxy ports and optional Let's Encrypt support.
cockpit-relay: image: alpine/socat container_name: cockpit-relay depends_on: - nginx-proxy command: "TCP-LISTEN:9090,fork,reuseaddr TCP:172.17.0.1:9090" expose: - "9090" environment: - VIRTUAL_HOST=somehost.somedomain - VIRTUAL_PROTO=https - LETSENCRYPT_HOST=somehost.somedomain - LETSENCRYPT_EMAILemail@example.com restart: unless-stopped logging: driver: journald networks: - webservices