Not possible to do port-forward to mongo32 about mongodb-container

[rhcarvalho]

This very likely applies to all other images as well (databases, language stacks).

[omron93]

@bparees @hhorak Should this be supported in our images?

[bparees]

@omron93 it seems like a reasonable ask to me given openshift's dependency on it for port forwarding (https://docs.openshift.com/enterprise/3.0/architecture/additional_concepts/port_forwarding.html#server-operation)

(see @jorgemoralespou? that's 2.)

[jorgemoralespou]

(@bparees I'm starting to get worried.)

[hhorak]

I don't see any reason to not do it either.
@jorgemoralespou Reading the docs, but still rather double-checking -- is it just about socat package installed in the image and no other changes need to be made?

[jorgemoralespou]

That @bparees would answer better. I'm not engineer so I have limited knowledge.

[bparees]

@hhorak i don't actually know myself, port-forwarding was at one point the domain of @ncdc though i'm not sure who it is now. It seems likely that socat would be the only pre-req though.

[ncdc]

socat has to live on the node. It does not need to be in individual "app" images.

[bparees]

whoops, i totally misread "The supported implementation currently in OpenShift invokes nsenter directly on the node host to enter the pod’s network namespace, then invokes socat to copy data between the stream and the pod’s port. " as implying it was entering the container and invoking socat, not just the network namespace.

Thanks @ncdc

So @jorgemoralespou this sounds like a more fundamental issue w/ your cluster. Closing this, you can open an issue in origin if you think it's a bug in cluster up or something.