{"action":"opened","issue":{"url":"https://api.github.com/repos/docker/for-mac/issues/627","repository_url":"https://api.github.com/repos/docker/for-mac","labels_url":"https://api.github.com/repos/docker/for-mac/issues/627/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-mac/issues/627/comments","events_url":"https://api.github.com/repos/docker/for-mac/issues/627/events","html_url":"https://github.com/docker/for-mac/issues/627","id":177061587,"number":627,"title":"Slow `docker-compose` performance while talking to a Moby VM whilst Mac Ethernet adapter is plugged in","user":{"login":"xeger","id":73368,"avatar_url":"https://avatars.githubusercontent.com/u/73368?v=3","gravatar_id":"","url":"https://api.github.com/users/xeger","html_url":"https://github.com/xeger","followers_url":"https://api.github.com/users/xeger/followers","following_url":"https://api.github.com/users/xeger/following{/other_user}","gists_url":"https://api.github.com/users/xeger/gists{/gist_id}","starred_url":"https://api.github.com/users/xeger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xeger/subscriptions","organizations_url":"https://api.github.com/users/xeger/orgs","repos_url":"https://api.github.com/users/xeger/repos","events_url":"https://api.github.com/users/xeger/events{/privacy}","received_events_url":"https://api.github.com/users/xeger/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-15T00:59:26Z","updated_at":"2016-09-15T00:59:26Z","closed_at":null,"body":"Beginning with the Docker for Mac beta25 update a few days back, I began to see a truly bizarre networking issue. When I run `docker-compose` on my Mac with an empty `DOCKER_HOST` env, operations take 10-60 times longer than they should. This problem does not manifest when I run standard `docker` commands; they're as fast as ever.\r\n\r\nTo add to the confusion, this issue _only_ manifests while my Thunderbolt Ethernet adapter is plugged in. If I remove it and rely on WiFI, the problem goes away.\r\n\r\n### Expected behavior\r\n\r\nInvoking `docker-compose` while Ethernet adapter is unplugged:\r\n\r\n```\r\n/tmp$ time docker-compose --verbose up -d test 2>&1 | ts\r\n...\r\nSep 14 17:52:46         0.95 real         0.22 user         0.05 sys\r\n```\r\n\r\n### Actual behavior\r\n\r\nOnce I plug in my Ethernet adapter:\r\n\r\n```\r\n/tmp$ time docker-compose --verbose up -d test 2>&1 | ts\r\n...\r\nSep 14 17:44:47        56.60 real         0.26 user         0.07 sys\r\n```\r\nAlmost 60x slower!\r\n\r\nEven stranger, the output from `docker-compose` seems to happen in bursts at 5-second intervals, regular as clockwork. It's almost like something is delaying or queuing the API calls it makes over `docker.sock`.\r\n\r\n### Steps to Reproduce\r\n\r\nCreate a trivial composition.\r\n\r\n```\r\nversion: \"2\"\r\nservices:\r\n  test:\r\n    image: busybox\r\n    command: \"sleep 60\"\r\n```\r\n\r\nPlug in a Thunderbolt adapter.\r\n\r\nRun `docker-compose up`\r\n\r\n### Information\r\n\r\n  - Diagnostic ID: 93F67582-B274-4714-9E27-30E98D1F16C5\r\n  - Ethernet adapter is \"Thunderbolt Ethernet\" (an Apple peripheral) model A-1433\r\n\r\nExtra info that your diagnostic may not have captured:\r\n\r\n```\r\n$ ls -la /var/run/docker.sock \r\nlrwxr-xr-x  1 root  daemon  57 Sep 14 17:39 /var/run/docker.sock -> /Users/tony/Library/Containers/com.docker.docker/Data/s60\r\n```\r\n\r\n```\r\n$ ifconfig\r\nlo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384\r\n\toptions=3<RXCSUM,TXCSUM>\r\n\tinet6 ::1 prefixlen 128 \r\n\tinet 127.0.0.1 netmask 0xff000000 \r\n\tinet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 \r\n\tnd6 options=1<PERFORMNUD>\r\ngif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280\r\nstf0: flags=0<> mtu 1280\r\nen0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500\r\n\tether ac:bc:32:7e:f2:f1 \r\n\tinet6 fe80::aebc:32ff:fe7e:f2f1%en0 prefixlen 64 scopeid 0x4 \r\n\tinet 10.10.12.180 netmask 0xfffffe00 broadcast 10.10.13.255\r\n\tnd6 options=1<PERFORMNUD>\r\n\tmedia: autoselect\r\n\tstatus: active\r\nen1: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500\r\n\toptions=60<TSO4,TSO6>\r\n\tether 6a:00:00:d1:ba:f0 \r\n\tmedia: autoselect <full-duplex>\r\n\tstatus: inactive\r\nen2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500\r\n\toptions=60<TSO4,TSO6>\r\n\tether 6a:00:00:d1:ba:f1 \r\n\tmedia: autoselect <full-duplex>\r\n\tstatus: inactive\r\np2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304\r\n\tether 0e:bc:32:7e:f2:f1 \r\n\tmedia: autoselect\r\n\tstatus: inactive\r\nawdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484\r\n\tether 36:ca:46:7e:cb:0a \r\n\tinet6 fe80::34ca:46ff:fe7e:cb0a%awdl0 prefixlen 64 scopeid 0x8 \r\n\tnd6 options=1<PERFORMNUD>\r\n\tmedia: autoselect\r\n\tstatus: active\r\nbridge0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500\r\n\toptions=63<RXCSUM,TXCSUM,TSO4,TSO6>\r\n\tether ae:bc:32:e7:de:00 \r\n\tConfiguration:\r\n\t\tid 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0\r\n\t\tmaxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200\r\n\t\troot id 0:0:0:0:0:0 priority 0 ifcost 0 port 0\r\n\t\tipfilter disabled flags 0x2\r\n\tmember: en1 flags=3<LEARNING,DISCOVER>\r\n\t        ifmaxaddr 0 port 5 priority 0 path cost 0\r\n\tmember: en2 flags=3<LEARNING,DISCOVER>\r\n\t        ifmaxaddr 0 port 6 priority 0 path cost 0\r\n\tnd6 options=1<PERFORMNUD>\r\n\tmedia: <unknown type>\r\n\tstatus: inactive\r\n```"}}
{"actor":{"display_login":"xeger"}}