{"action":"created","issue":{"url":"https://api.github.com/repos/aacebedo/dnsdock/issues/89","repository_url":"https://api.github.com/repos/aacebedo/dnsdock","labels_url":"https://api.github.com/repos/aacebedo/dnsdock/issues/89/labels{/name}","comments_url":"https://api.github.com/repos/aacebedo/dnsdock/issues/89/comments","events_url":"https://api.github.com/repos/aacebedo/dnsdock/issues/89/events","html_url":"https://github.com/aacebedo/dnsdock/issues/89","id":197688619,"number":89,"title":"Unable to run dnsdock due to \"EADDRNOTAVAIL\" error on docker-for-mac","user":{"login":"vincentchalamon","id":407859,"avatar_url":"https://avatars.githubusercontent.com/u/407859?v=3","gravatar_id":"","url":"https://api.github.com/users/vincentchalamon","html_url":"https://github.com/vincentchalamon","followers_url":"https://api.github.com/users/vincentchalamon/followers","following_url":"https://api.github.com/users/vincentchalamon/following{/other_user}","gists_url":"https://api.github.com/users/vincentchalamon/gists{/gist_id}","starred_url":"https://api.github.com/users/vincentchalamon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vincentchalamon/subscriptions","organizations_url":"https://api.github.com/users/vincentchalamon/orgs","repos_url":"https://api.github.com/users/vincentchalamon/repos","events_url":"https://api.github.com/users/vincentchalamon/events{/privacy}","received_events_url":"https://api.github.com/users/vincentchalamon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2016-12-27T11:19:51Z","updated_at":"2016-12-30T07:30:40Z","closed_at":null,"body":"Hi,\r\n\r\nI'm trying to run dnsdock:v1.16.1-amd64 on docker-for-mac, but I always have the following error:\r\n```\r\ndocker: Error response from daemon: driver failed programming external connectivity on endpoint dnsdock (120520037b1d620dffbd11d1472e700194a3908daa1c40becb0623be0d2124d7): Error starting userland proxy: Bind for 172.17.0.1:53: unexpected error (Failure EADDRNOTAVAIL).\r\n```\r\n\r\nI tried with `172.17.0.1` (`bridge` network gateway) and other network IP addresses, I always have the same error.\r\n\r\n**Environment:**\r\n- docker for mac v1.12.5 (14777) stable 3e6f00c1dc\r\n- docker v1.12.5, build 7392c3b\r\n- docker-compose v1.9.0, build 2585387\r\n- osx el capitan v10.11.6\r\n\r\n**I don't have this error on docker-toolbox.**"},"comment":{"url":"https://api.github.com/repos/aacebedo/dnsdock/issues/comments/269741276","html_url":"https://github.com/aacebedo/dnsdock/issues/89#issuecomment-269741276","issue_url":"https://api.github.com/repos/aacebedo/dnsdock/issues/89","id":269741276,"user":{"login":"aacebedo","id":1217680,"avatar_url":"https://avatars.githubusercontent.com/u/1217680?v=3","gravatar_id":"","url":"https://api.github.com/users/aacebedo","html_url":"https://github.com/aacebedo","followers_url":"https://api.github.com/users/aacebedo/followers","following_url":"https://api.github.com/users/aacebedo/following{/other_user}","gists_url":"https://api.github.com/users/aacebedo/gists{/gist_id}","starred_url":"https://api.github.com/users/aacebedo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aacebedo/subscriptions","organizations_url":"https://api.github.com/users/aacebedo/orgs","repos_url":"https://api.github.com/users/aacebedo/repos","events_url":"https://api.github.com/users/aacebedo/events{/privacy}","received_events_url":"https://api.github.com/users/aacebedo/received_events","type":"User","site_admin":false},"created_at":"2016-12-30T07:30:40Z","updated_at":"2016-12-30T07:30:40Z","body":"There is no virtualization on docker for linux, the kernel itself provides the capabilities of creating process and user namespaces. That is one of the main differences between virtualization and containerization.\r\nOn docker for mac and according their docs, they switched from virtualbox to hyperkit, there is still a virtualization layer because the macOS kernel is not able to provide namespace capabilities.\r\n\r\nTo answer your question, just remind that dnsdock is a only a DNS resolver. If you want any machine to obtain IPs in DNS responses, it shall send its requests to the container in which dnsdock is running (ie the IP you shall put in your dns resolver is the one of the dnsdock container). Then the IP corresponding to the requested domain and contained in the DNS response given by dnsdock will be either the IP of the container itself, or the value you've given to the com.dnsdock.ip_addr label.\r\n\r\nAs mentionned in the docker for mac documentation there is now docker0 bridge interface on your macOS host as this interface is created within the hyperkit VM running docker. They also say that there are some issues about networking on this setup (ie you cannot have per container IP addressing on  Mac).\r\nYou may try to switch to docker-toolbox or to install a linux in a VM and use docker inside. You may also try to use traefik (https://traefik.io/) to reroute your domain traffic to different container's instances"}}
{"actor":{"display_login":"aacebedo"}}