Request to connect destination to UDS (Unix domain sockets) #177
Description
I have found #3 but I believe it is closed without implementing the feature.
We use containers that are connecting to aws iot. To be able to make the SSH work, we need to have a separate network space in the container. Otherwise it collides with the host's network space. In other words, the container cannot listen on port 22 because the host is already listening to it. Two solutions to it,
a) You give a new network namespace to the container that the container owns but setting this network adds complexity to the container setup.
b) Use new IPC namespace and have SSH listen on UDS which is very straightforward.
localproxy cannot connect to UDS, therefore we cannot attach SSH to it if we don't have a new network namespace.
From the libc perspective, connecting to a socket vs connecting to a UDS shouldn't matter but probably localproxy has some verification against the desired service.
Thank you