Support for sharing unix sockets

[BouncyLlama]

Expected behavior

When mounting a directory containing unix sockets the sockets should function the same as they do on a Linux host.

Actual behavior

The socket is 'there', but non-functional.

Information

After reading several forum threads, it appears that there is a workaround with socat over TCP, but this is rather slow.

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 #410 which asks specifically for SSH_AUTH_SOCK to be supported.

Host OS: Mac OSX 10.10.5

Steps to reproduce the behavior

1. mount a directory containing unix sockets like so: '-v "/directorywithsockets:/otherdirectory"'
2. attempt to send data to/from the host/container via the socket

[dsheets]

This is on the roadmap.

[udondan]

Interestingly, even a socket created in the container is non-functional if it was created on a mounted volume of the host.

[jippi]

Any ETA on this? :)

Currently it's blocking hashicorp/nomad#1091 and other projects :)

[dsheets]

This is currently scheduled for resolution in November. Sorry for the delay.

[jippi]

@dsheets okay, will it be available in beta builds beforehand?

[dsheets]

Our goal is to ship it in beta builds in November.

[jippi]

amazing @dsheets - if you need any testing or otherwise beforehand, I'm willing to help out!