{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/21357","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/21357/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/21357/comments","events_url":"https://api.github.com/repos/docker/docker/issues/21357/events","html_url":"https://github.com/docker/docker/issues/21357","id":142252896,"number":21357,"title":"docker overylay network ping failed when the container ip is same with host ip","user":{"login":"LionHeartFXCX","id":11309761,"avatar_url":"https://avatars.githubusercontent.com/u/11309761?v=3","gravatar_id":"","url":"https://api.github.com/users/LionHeartFXCX","html_url":"https://github.com/LionHeartFXCX","followers_url":"https://api.github.com/users/LionHeartFXCX/followers","following_url":"https://api.github.com/users/LionHeartFXCX/following{/other_user}","gists_url":"https://api.github.com/users/LionHeartFXCX/gists{/gist_id}","starred_url":"https://api.github.com/users/LionHeartFXCX/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LionHeartFXCX/subscriptions","organizations_url":"https://api.github.com/users/LionHeartFXCX/orgs","repos_url":"https://api.github.com/users/LionHeartFXCX/repos","events_url":"https://api.github.com/users/LionHeartFXCX/events{/privacy}","received_events_url":"https://api.github.com/users/LionHeartFXCX/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-21T04:20:40Z","updated_at":"2016-03-21T05:54:05Z","closed_at":null,"body":"<!--\r\nIf you are reporting a new issue, make sure that we do not have any duplicates\r\nalready open. You can ensure this by searching the issue list for this\r\nrepository. If there is a duplicate, please close your issue and add a comment\r\nto the existing issue instead.\r\n\r\nIf you suspect your issue is a bug, please edit your issue description to\r\ninclude the BUG REPORT INFORMATION shown below. If you fail to provide this\r\ninformation within 7 days, we cannot debug your issue and will close it. We\r\nwill, however, reopen it if you later provide the information.\r\n\r\nFor more information about reporting issues, see\r\nhttps://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues\r\n\r\n---------------------------------------------------\r\nBUG REPORT INFORMATION\r\n---------------------------------------------------\r\nUse the commands below to provide key information from your environment:\r\nYou do NOT have to include this information if this is a FEATURE REQUEST\r\n-->\r\n**Describe**\r\nI create an overylay network with Docker-toolbox,but when the container's ip is same with host's ip, the container can't ping each other.\r\nI have try another container ip addresses that are not same with the machine's ip, succeed. So I am confused that is Docker's overylay network does not support the same ip with the host ip? or I can do other things to solve the problem? or the virtualbox's version is too old?\r\n\r\n**Output of `docker version`:**\r\n\r\n```\r\nClient:\r\n Version:      1.10.3\r\n API version:  1.22\r\n Go version:   go1.5.3\r\n Git commit:   20f81dd\r\n Built:        Thu Mar 10 21:49:11 2016\r\n OS/Arch:      linux/amd64\r\n\r\nServer:\r\n Version:      1.10.3\r\n API version:  1.22\r\n Go version:   go1.5.3\r\n Git commit:   20f81dd\r\n Built:        Thu Mar 10 21:49:11 2016\r\n OS/Arch:      linux/amd64\r\n```\r\n\r\n\r\n**Output of `docker info`:**\r\n\r\n```\r\nContainers: 3\r\n Running: 3\r\n Paused: 0\r\n Stopped: 0\r\nImages: 3\r\nServer Version: 1.10.3\r\nStorage Driver: aufs\r\n Root Dir: /mnt/sda1/var/lib/docker/aufs\r\n Backing Filesystem: extfs\r\n Dirs: 33\r\n Dirperm1 Supported: true\r\nExecution Driver: native-0.2\r\nLogging Driver: json-file\r\nPlugins:\r\n Volume: local\r\n Network: overlay bridge null host\r\nKernel Version: 4.1.19-boot2docker\r\nOperating System: Boot2Docker 1.10.3 (TCL 6.4.1); master : 625117e - Thu Mar 10 22:09:02 UTC 2016\r\nOSType: linux\r\nArchitecture: x86_64\r\nCPUs: 1\r\nTotal Memory: 996.1 MiB\r\nName: node1\r\nID: TR2A:PW42:XWNX:JPSJ:MOJL:D6EH:YO6N:DDY4:4PCG:U7XY:LTPP:I44F\r\nDebug mode (server): true\r\n File Descriptors: 45\r\n Goroutines: 86\r\n System Time: 2016-03-21T03:16:08.063964088Z\r\n EventsListeners: 1\r\n Init SHA1:\r\n Init Path: /usr/local/bin/docker\r\n Docker Root Dir: /mnt/sda1/var/lib/docker\r\nLabels:\r\n provider=virtualbox\r\nCluster store: consul://192.168.99.101:8500\r\nCluster advertise: 192.168.99.103:2376\r\n```\r\n\r\n**Additional environment details (AWS, VirtualBox, physical, etc.):**\r\nI am using docker-toolbox 1.10.3 with VirtualBox4.3.36 .\r\nfew days ago, I am using VirtualBox 5.0.16,but it suddenly can not work, I found many ways to slove the problem,but no result. So I change the version of VB, it work normally.\r\nthe above content I paste is one of my virtual machines. I create 4 machines, one as a discovery service machine, one as a swarm manager,and others are nodes.\r\n\r\n\r\nSteps :\r\n1.Create a container test1 on machine 192.168.99.103 with --ip option and --net option, the container ip address is the same with the host ip address.(the container is created successfully)\r\n2.Create a container test2 on machine 192.168.99.102 with --ip option and --net option, the container ip address is the same with the host ip address.(the container is created successfully)\r\n3.test1 ping test2 or test2 ping test1\r\n\r\n\r\n received:\r\nping of both failed\r\n\r\n expected:\r\nping of both succeed\r\n\r\nAdditional :\r\nforgive me my poor english, please help me, I'm running out of time.\r\n@thaJeztah @mavenugo"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/199137281","html_url":"https://github.com/docker/docker/issues/21357#issuecomment-199137281","issue_url":"https://api.github.com/repos/docker/docker/issues/21357","id":199137281,"user":{"login":"mavenugo","id":5056191,"avatar_url":"https://avatars.githubusercontent.com/u/5056191?v=3","gravatar_id":"","url":"https://api.github.com/users/mavenugo","html_url":"https://github.com/mavenugo","followers_url":"https://api.github.com/users/mavenugo/followers","following_url":"https://api.github.com/users/mavenugo/following{/other_user}","gists_url":"https://api.github.com/users/mavenugo/gists{/gist_id}","starred_url":"https://api.github.com/users/mavenugo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mavenugo/subscriptions","organizations_url":"https://api.github.com/users/mavenugo/orgs","repos_url":"https://api.github.com/users/mavenugo/repos","events_url":"https://api.github.com/users/mavenugo/events{/privacy}","received_events_url":"https://api.github.com/users/mavenugo/received_events","type":"User","site_admin":false},"created_at":"2016-03-21T05:54:05Z","updated_at":"2016-03-21T05:54:05Z","body":"@LionHeartFXCX As per your expectations, the subnet used inside of the overlay network should not ideally overlap with that of the other overlay network or the host subnet for that matter. But I believe the vtep-endpoint address could be the exception (I have to try it myself to confirm). My immediate guess is that since the ip-addresses `192.168.99.102` and `192.168.99.103` are vtep endpoints (`--cluster-advertise`), it is possible that the ip->mac is resolved to the host-namespace and it might conflict with the container space.\r\n\r\nSince you are using the `--ip`, I assume that you are intentionally using the `--subnet=192.168.99.0/24` while creating the overlay network. Is there a specific reason that you have such a requirement to have the same subnet as that of the host ? And if so, is there a reason to have the same ip-address as that of the VTEP endpoint ?\r\n\r\nI will try and confirm the above observation myself."}}