moby: Docker sending network request to wrong containers

I am just observing a very strange issue where say containers 1 --> port 2401 2 --> port 2402 3 --> port 2403

When i send an http request to 127.0.0.1:2401. Somehow the traffic goes to 127.0.0.1:2402

I then stop container 1 and then traffic goes to 2404 as requested. However after a few minutes,

Container 1 starts itself again without any docker start request explicitly. When container 1 starts itself, it then accepts any incomming request.

Any thoughts on this?

Output of docker version:

Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 152
Images: 33
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 491
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-24-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 8
Total Memory: 31.36 GiB
Name: buf460
ID: YFXS:R7GN:SAIB:F5Z3:TW24:H7QS:ELJP:5ENZ:2EP3:C7KW:RZSW:CK7H

Additional environment details (AWS, VirtualBox, physical, etc.):

Steps to reproduce the issue: 1. 2. 3.

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 1
Comments: 16 (5 by maintainers)

Most upvoted comments

By the way guys issue 22325 is exactly the problem i reported weeks ago. I spent days blaming myself this could never be a docker issue because somebody would have long reported it.

In my case i almost lost my job when a client opened his website and to his amazement another clients website was showing up, i had to beg to keep my job.

The only way out of this issue is to use host networking. Of course host networking is also a real bummer when a dubious client launches his app and tries to launch mini servers on other ports which might be open.

mutex007 on May 1, 2016