Docker Community Forums

Share and learn in the Docker community.

Incoming Network Connections Fail With Native Port Forwarding

(Breser) #1

Expected behavior

Incoming network connections when using the native port forwarding should work.

Actual behavior

We’re using gpload inside a docker container. The way it works is it contacts Greenplum and tells it where to connect and then various instances on the database connect back to the Docker container to retrieve data. All of these connections come to a single port on the Docker container and are HTTP traffic.

Some of these connections fail, pretty much immediately. Basically the 3 way handshake comes in and then immediately an RST is sent.

Not all the connections fail, but some.

Packet capture is below:


OS X: version 10.10.5 (build: 14F1605) version v1.11.1-beta12
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160519-161327.tar.gz
Most specific failure is: No error was detected
Your unique id is: DF1647D1-DD54-4F2A-8BAB-6ADCFB35CB16
Please quote this in all correspondence.

Steps to reproduce the behavior

Unfortunately I can’t provide a reproduction recipe since currently the only way I know to reproduce this is to use gpload. I’m positive it’s not my infrastructure since if I turn off native port forwarding and put an HTTP proxy between everything works. I’d spoke with two Docker employees at OSCon about this problem and they suggested that I make this bug report if I could still reproduce this in beta12. I can reproduce this locally every single time. So if there’s more I can do on my end to help diagnose this let me know.