macOS unix socket error

[monoflash]

Service running in the docker container, service opened unix socket.
On the host machine, binding the folder, in which the unix socket is placed.
Host machine is macOS, on the host machine, unix socket is visible in folder, but there is no access to communicate with unix socket.
If run the client in the another docker container and provide it with the same socket, then the socket is available and working.
If the host machine is running on linux, there is no such problem.

Version 17.07.0-ce-rc2-mac22 (18909)
Channel: edge
d9a9cf3b45

[ebriney]

Hi @monoflash :
osxfs, the component developed for filesharing doesn't yet support host<->vm unix socket sharing.
This on the roadmap but there is ETA for now.

[dsheets]

https://docs.docker.com/docker-for-mac/osxfs/#file-types describes the behavior of sockets in shared file system fragments. This is a duplicate of #483 which is tracking the development of this feature. Thanks for your report and please subscribe to #483 for future updates.

[JulyIghor]

Hi @monoflash :
osxfs, the component developed for filesharing doesn't yet support host<->vm unix socket sharing.
This on the roadmap but there is ETA for now.

any news on this?

[monoflash]

Why a question to me?
I’m not a docker developer, and moreover, for the macOS, docker it has been working extremely badly for half a year now...
But the problem with the unix socket remained the same, new problems were added.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked