[Bug 1387805] Re: docker.io containers cannot use local dnsmasq

2015-06-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: docker.io (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387805

Title:
  docker.io containers cannot use local dnsmasq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1387805/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1387805] Re: docker.io containers cannot use local dnsmasq

2015-06-02 Thread Paul Annekov
Second solution does not work for me. First solution (with
NetworkManager.conf) perfectly solves my problem.

OS: Xubuntu 15.04
Docker: 1.7.0-dev, build 5e06332 (from ppa)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387805

Title:
  docker.io containers cannot use local dnsmasq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1387805/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1387805] Re: docker.io containers cannot use local dnsmasq

2015-06-02 Thread Paul Tagliamonte
127.0.0.1 inside the container isn't the same as 127.0.0.1 inside the
container.

I'm OK calling this a container misconfiguration.

I've not tried, but try setting dnsmasq to bind to the docker0 interface
(likely bind to 172.17.42.1) and hit that IP.

Otherwise you're hitting 127.0.0.1 in the container, which isn't what
you want (or where dnsmasq is bound)

This is part of network namespacing.

Closing the ticket, thanks!

** Changed in: docker.io (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387805

Title:
  docker.io containers cannot use local dnsmasq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1387805/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1387805] Re: docker.io containers cannot use local dnsmasq

2015-06-02 Thread Paul Tagliamonte
127.0.0.1 inside the container isn't the same as 127.0.0.1 inside the
container.

I'm OK calling this a container misconfiguration.

I've not tried, but try setting dnsmasq to bind to the docker0 interface
(likely bind to 172.17.42.1) and hit that IP.

Otherwise you're hitting 127.0.0.1 in the container, which isn't what
you want (or where dnsmasq is bound)

This is part of network namespacing.

Closing the ticket, thanks!

** Changed in: docker.io (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to docker.io in Ubuntu.
https://bugs.launchpad.net/bugs/1387805

Title:
  docker.io containers cannot use local dnsmasq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1387805/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs