{"action":"opened","issue":{"url":"https://api.github.com/repos/docker/for-mac/issues/2721","repository_url":"https://api.github.com/repos/docker/for-mac","labels_url":"https://api.github.com/repos/docker/for-mac/issues/2721/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-mac/issues/2721/comments","events_url":"https://api.github.com/repos/docker/for-mac/issues/2721/events","html_url":"https://github.com/docker/for-mac/issues/2721","id":308241501,"number":2721,"title":"Feature Request: Local DNS server option","user":{"login":"tcldr","id":26437279,"avatar_url":"https://avatars2.githubusercontent.com/u/26437279?v=4","gravatar_id":"","url":"https://api.github.com/users/tcldr","html_url":"https://github.com/tcldr","followers_url":"https://api.github.com/users/tcldr/followers","following_url":"https://api.github.com/users/tcldr/following{/other_user}","gists_url":"https://api.github.com/users/tcldr/gists{/gist_id}","starred_url":"https://api.github.com/users/tcldr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tcldr/subscriptions","organizations_url":"https://api.github.com/users/tcldr/orgs","repos_url":"https://api.github.com/users/tcldr/repos","events_url":"https://api.github.com/users/tcldr/events{/privacy}","received_events_url":"https://api.github.com/users/tcldr/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-24T09:01:40Z","updated_at":"2018-03-24T09:01:40Z","closed_at":null,"author_association":"NONE","body":"## Feature Request\r\n\r\n*This is related to #155 but takes the proposal a step further*\r\n\r\nI'm using docker to provide my local development environments. Currently, remembering and assigning ports for the various environments requires a bit of juggling and is a bit of a pain. What I'd like to be able to do is have a simple mechanism for assigning a .test domain name to a particular project.\r\n\r\nIt would be great if Docker for Mac facilitated this. Obviously it would need to be done in such a way that doesn't interfere with existing features.\r\n\r\nI expect this would require running an additional container with a dns server and then rerouting host dns queries to it – but anything that works is fine by me.\r\n\r\nHow I imagine this could work user experience wise:\r\n\r\n1. User creates docker compose project. As usual, a network is assigned – either `my_app_default` or another user-defined name.\r\n2. A new docker specific 'hosts' file (or ideally, a preferences panel within the Docker for Mac app) allows for the mapping of project name to domain name. i.e `*.my_app_default.test` points to `my_app_default`.\r\n3. User can now access containers via domain name. i.e. `www.my_app_default.test` points to the container named `www` in the `my_app_default` docker network, or `db.my_app_default.test` points to... you get the idea!"}}
{"actor":{"display_login":"tcldr"}}