{"action":"closed","issue":{"url":"https://api.github.com/repos/rancherio/rancher/issues/54","labels_url":"https://api.github.com/repos/rancherio/rancher/issues/54/labels{/name}","comments_url":"https://api.github.com/repos/rancherio/rancher/issues/54/comments","events_url":"https://api.github.com/repos/rancherio/rancher/issues/54/events","html_url":"https://github.com/rancherio/rancher/issues/54","id":55530013,"number":54,"title":"Allow binding to a specific interface","user":{"login":"hbokh","id":519955,"avatar_url":"https://avatars.githubusercontent.com/u/519955?v=3","gravatar_id":"","url":"https://api.github.com/users/hbokh","html_url":"https://github.com/hbokh","followers_url":"https://api.github.com/users/hbokh/followers","following_url":"https://api.github.com/users/hbokh/following{/other_user}","gists_url":"https://api.github.com/users/hbokh/gists{/gist_id}","starred_url":"https://api.github.com/users/hbokh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hbokh/subscriptions","organizations_url":"https://api.github.com/users/hbokh/orgs","repos_url":"https://api.github.com/users/hbokh/repos","events_url":"https://api.github.com/users/hbokh/events{/privacy}","received_events_url":"https://api.github.com/users/hbokh/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-01-26T20:03:18Z","updated_at":"2015-01-26T21:58:16Z","closed_at":"2015-01-26T21:58:16Z","body":"On CoreOS v550.0.0 rancher binds to the `docker0` interface, which has an 172.17.x.y address.\r\nI want to make rancher bind to `ens192`, which has a 192.168.x.y DHCP-leased address and is accessible inside my LAN-network.\r\nSince I can not access the 172.17.x.y range directly, all containers binded to the network IN that host are unreachable.\r\nIs binding to interface `ens192` an option somehow or is this a CoreOS-specific issue?"}}