https://github.com/tobilg/docker-expose-socket
Docker image for exposing the Docker UNIX socket via TCP without having to reconfigure the daemon itself.
https://github.com/tobilg/docker-expose-socket
Last synced: 7 months ago
JSON representation
Docker image for exposing the Docker UNIX socket via TCP without having to reconfigure the daemon itself.
- Host: GitHub
- URL: https://github.com/tobilg/docker-expose-socket
- Owner: tobilg
- License: mit
- Created: 2015-10-06T09:47:00.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2015-10-07T12:04:38.000Z (almost 10 years ago)
- Last Synced: 2025-01-31T04:51:47.241Z (8 months ago)
- Language: Shell
- Size: 137 KB
- Stars: 2
- Watchers: 3
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Expose Docker socket via TCP
Sometimes it's complicated to run TLS-supported Docker Remote API queries. To facilitate this without having to change the Docker daemon's settings, use this image to expose the Docker socket via TCP.
Also, there seem to be some bugs in the current Docker version.
See
* https://github.com/docker/docker/issues/16118
## Running
The image's internal port of the Docker socket is `12375`. You can remap the port via `-p 1234:12375` for example. This would expose the Docker socket on port `1234` on the Docker host.
Run `docker run -d -v /var/run/docker.sock:/var/run/docker.sock -p 1234:12375 --name expose -t tobilg/expose-socket` on the Docker/Boot2Docker host.
**Attention: This is exposing your Docker socket (meaning full access!) to the public! Don't do this on public networks etc. This image is just intended for quick testing of the Docker Remote API!***