Docker binds only on IPV6

[ebuildy]

docker version:

Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64

docker info:

Containers: 0
Images: 35
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 35
 Dirperm1 Supported: true
Execution Driver: native-0.2
Kernel Version: 3.19.0-21-generic
Operating System: Ubuntu 15.04
CPUs: 1
Total Memory: 668.4 MiB
Name: prod-docker-ad
ID: YSJS:KYUS:DXPQ:CQRH:5AUS:2TRW:PY3Q:CBN5:ORPH:EF4S:VZIW:L3ZF
WARNING: No swap limit support

uname -a:

Linux prod-docker-ad 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Running on Microsoft Azure cloud under a public load-balancer.

Step to produce the error:

1. docker run -d -p 80:8080 --name admin_rancher rancher/server

Result received:

Result excepted:

Where ssh is listening on both IPV4 and IPV6, Docker only on IPV6. I don't know if it's a bug or not, but how can I force Docker to use only IPV4 ? (I have already disable and blacklist IPV6).

[GordonTheTurtle]

Hi!

Please read this important information about creating issues.

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

This is an automated, informational response.

Thank you.

For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

---

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment:

docker version:
docker info:
uname -a:

Provide additional environment details (AWS, VirtualBox, physical, etc.):

List the steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:

Provide additional info you think is important:

----------END REPORT ---------

#ENEEDMOREINFO

[cpuguy83]

This is a dup of #2174, and as stated in that one this is just an issue with netstat.
If something is not connecting correctly I'd just the service in the container is actually working properly rather than netstat.
Closing as this is a dup.