Re: [atomic-devel] Addition of socat to Atomic?

[Clayton Coleman <ccoleman redhat com>]

This is being run by the Kubelet and is the "we need to hook container A to an incoming HTTPS SPDY stream for transport back to the edge".  It would be really a dependency of the Kubelet, at least until we have a socat/nsenter equivalent that lets us direct enter a namespace and connect out.

----- Original Message -----
> Hi,
> 
> On Fri, Mar 20, 2015, at 09:13 AM, Andy Goldstein wrote:
> > Hi all,
> > 
> > For OpenShift 3, we are currently using socat on the OpenShift nodes to
> > enable port forwarding from a user’s machine to ports in containers. Would
> > it be possible to add socat to Atomic?
> 
> Did you investigate a toolbox container for this?  With `--pid=host` and
> `--net=host`, you can run a container with socat inside that starts with the
> host network stack.  Then via a combination of `--pid=host` and `nsenter`,
> you can access *other* container's network namespaces.
> 
> It'd be even easier I think if `socat` directly learned about `setns()`,
> similar to
> https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-February/msg00064.html
> 
> 
>