Re:How to pass docker.sock to your containers while keeping ...
by titpetric on Tuesday April 26, 2016 @02:50AM
(#11569908)
In thise case, you can't use a read only mount. The underlying protocol is HTTP, which means you must write a request to the socket to get a response. You can use read only mounts for `/proc` however, which just spits out data. I use it for titpetric/netdata for example.
[ Parent
| on HN ]
Re:How to pass docker.sock to your containers while keeping ...
by fpoling on Tuesday April 26, 2016 @03:58AM
(#11570145)
This is wrong, I use read-only mounts for Unix sockets all the time. Such mount does not prevent reading-writing to the socket. What the read-only mount prevents is modification of meta-information for the socket file like changing ownership or permissions or ability to delete it.