ProtocolMetaData returned by Container is wrong when using PortForwarding #12
Labels
Milestone
Comments
aslakknutsen
added a commit
to aslakknutsen/arquillian-cube
that referenced
this issue
Nov 8, 2014
The Container only knows about the ports it self is bound to, not how Docker is remapping them from the outside. When e.g. the Container is bound to port 8080 inside Docker and Docker PortForward from external port 8081 to internal 8080 the ProtocolMetaData is of. This effects the ServletProtocol which is attempting to use this information to communicate with the in-container test case as well as URL injection on the client side via @ArquillianResource. When the ProtocolMetaData is created, the object is intercepted bu Cube to update the data based on the port we know are being forwarded. fixes arquillian#12
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Container it self only knows which ports it is bound to inside the Docker image, not which ports are opened from the outside via PortForward.
This effects the ServletProtocol when attempting to communicate with incontainer test cases and @ArquillianResource URL injection.
The text was updated successfully, but these errors were encountered: