It seems that the most prevalent use case for this feature is for developers to develop and test containers locally on a single-user MacOS laptop.

attempt to send data to/from the host/container via the socket.

mount a directory containing unix sockets like so: '-v '/directorywithsockets:/otherdirectory'.

Host OS: Mac OSX 10.10.5 Steps to reproduce the behavior The documentation has this to say: 'Socket files and named pipes only transmit between containers and between OS X processes - no transmission across the hypervisor is supported, yet' Hopefully this is a planned feature already, but I did not see any existing issues open in this tracker for this particular issue, although it relates to which asks specifically for SSH_AUTH_SOCK to be supported. Information After reading several forum threads, it appears that there is a workaround with socat over TCP, but this is rather slow. Actual behavior The socket is 'there', but non-functional. Each other via UNIX domain sockets when they are in different network namespaces.Įxpected behavior When mounting a directory containing unix sockets the sockets should function the same as they do on a Linux host. Sharing unix socket via docker volume - permission denied. If you need to access the Docker daemon remotely, you need to enable the tcp Socket.

or theoretically, u could run socat in its own container, then share the socket between your app's container and socat's container.Jump to Daemon socket option - By default, a unix domain socket (or IPC socket) is created at /var/run/docker.sock, requiring either root permission, or docker group membership.

an init system / process manager inside the container.

some clever scripting inside the container to run ur program and socat.

However this introduces another process you have to manage. Then use socat inside the container to map the host's port to a socket within the container.

You can use socat on the host to map a socket on the host to a port on the host. The previous technique can be augmented for other programs that are adamant about using sockets.

I dont know what it is for docker on linux. Docker containers can see their host at on docker desktop for mac and windows.

Other programs are also designed to work over a network as well (like X11 or pulseaudio).

The linked github issue describes a ssh agent specific workaround that is part of docker now.

Sharing (mounting?) Unix sockets between the macos host and the linux vm in which docker containers are run is not possible at this time.

Docker unix domain socket